What I am trying to do is authenticate users using my own database. There I am following the guidelines mentioned in Articles at Auth0 web site here. I followed all the steps mentioned there for msql connection (including configuring my firewall to allow access to the specified addresses). Actually first I created the ‘Login’ database action script. But when I am going to ‘try’ it, the following error appears.
Hey there ejcjayathma! “Request to Webtask got ESOCKETTIMEDOUT” is commonly thrown when there is an issue in requests made from a custom database connection script, hook, or rule. Is there by chance any further log information or details you could share with us that may help in troubleshooting what you’re experiencing?
On first glance your script looks fine, can we try adding some console.log()s to see if we can find more details on where the point of failure might be? You can also take a look at Real-time Webtask Logs extension to help gather more feedback as the webtask runs.
It looks like you’re getting connecting Error because that’s what you’re telling it to output as the error. I suggest having it dump the error it finds (via the err value you’re passing)
The nested connection.connect() may have caused the [Error] Cannot enqueue Handshake after already enqueuing a Handshake. error. When you get a moment @ejcjayathma can you remove that and see what output we get from there?
So moving forward we would remove this section for the test:
While investigating this issue I need to dig a little deeper, when you get a moment can you DM me your tenant name? Is it possible that you have a rule active that is interfering with your webtask? Thanks!
Hey @jerac.dialino@ejcjayathma, and @sonali4294, I am happy to take a look at this issue with you but I do need more information on the challenge you are facing. When you get a chance can you please direct message me your tenant names? Also Is it possible that you have an active rule that could be interfering with your webtask? Any additional information is appreciated so we can help you get this worked out. Thanks!
@jerac.dialino after looking at the script you sent and investigating your tenant I did not see an active custom db implementation. This presents a challenge when reproducing the issue. Often times when this error is presented with a custom database active it can mean the customer database took too long to respond a threw the ESOCKETTIMEOUT error. That being said I would be happy to investigate this further if we had more details available. Thanks in advance!