Failed Signup - Error: Client request error: socket hang up at createHangUpError [...]

[aurelien]

Hello,

Since Sunday, 1st sept at 09:12am UTC, signup is broken on our production environment. On Auth0 logs, we’ve got several logs “Failed signup”. The staging tenant seems to be not concerned. We use Lock to perform signin / signup.

Here the auth0 log :

Description : Error: Client request error: socket hang up at createHangUpError (_http_client.js:342:15) at Socket.socketOnEnd (_http_client.js:437:23) at emitNone (events.js:111:20) at Socket.emit (events.js:208:7) at endReadableNT (_stream_readable.js:1064:12) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickDomainCallback (internal/process/next_tick.js:219:9)

On the browser-side, the following request failed (sent by Lock) :

On the client, there is a 400 Erreur with the request : https://login.DOMAIN.com/dbconnections/signup => Universal Login domain

Request params :
client_id: “qyAGNxwDMO53XiQE8cd3IcSAaut6WELe”
connection: “Username-Password-Authentication”
email: “myadress+201909021559@gmail.com”
password: “***********”

Response :
{“fromSandbox”:true,“statusCode”:400}

I need some input to identify the origin of this issue.

Regards,
Aurélien

[dan.woda]

Hi @aurelien,

Can you please provide the name of your tenant to me via a DM.

Thanks,
Dan

[aurelien]

Hi Dan,

João Angelo (from Auth0) help me to resolve this issue.

For all concerned by this error, in my context, this error resulted from a custom database (Auth0 advanced settings) that had been deleted. The consequence was signup and email/pwd login were broken.

Since all users from the legacy DB were migrated, I just updated the custom scripts “Login” and “Get user” as described in Configure Automatic Migration from Your Database

Thank you to all the Auth0 support team for the help.

[dan.woda]

Excellent. Thank you very much for posting the solution!