"ETIMEDOUT" and "PROTOCOL_SEQUENCE_TIMEOUT" errors

[Alex-Pqn]

Hello, I have been having a problem since this afternoon that had never happened to me. It's quite weird because I use a code that I had previously done, the one worked perfectly and now it doesn't work anymore (I'm afraid the problem comes from the side of the host) but by doubt I'm asking the problem here, I may have been wrong about some things.

to know: In my case, I try to communicate from my Node.js API locally with my MySQL database which it is hosted at PlanetHoster.

My configuration file looks like this basically :

My controller in which I run a very simple query to test:

I'm using a pool here, which I've already tried with createConnection as well.

In running this, here's the error I get :

After having this error, I decided to increase the value of "acquireTimeout" to "10000000" in my configuration file and now the error is no longer "PROTOCOL_SEQUENCE_TIMEOUT" but "ETIMEDOUT", with the ip of my server (hidden in red) and the port (the identifiers are therefore correct I think) but the problem is there, it does not work...

I don't know where to look, I tested a lot of things (including the issues posted here about this error) but nothing works, nothing solves the problem (I also tried with the url in string format instead of the configuration file).

Thank you very much to the people who will take the time to answer me, any help is welcome !

[dougwilson]

Hi @Alex-Pqn sorry you are having trouble. Typically these time outs mean there is either an issue on the MySQL server side or in the network path between the machine running Node.js and the MySQL server (things like the network path, firewalls dropping packets, etc.). The only real way to start to diagnose this type of issue is to get your network team involved if you have one, otherwise to use packet capture tools on both ends to see what is happening to the packets. For example, if you see packets transmitted from your Node.js machine but they never arrive at the MySQL machine, then you'll want to consult your network diagram of systems between there are check if there are network management rules that drop those particular packets.

[Alex-Pqn]

Okay I see, I honestly don't know very well about networking and I don't see where to start to make a diagnosis. Do you have a lead? Maybe also contact my web host for more information if it comes from their side?

Thanks for the quick response.

[dougwilson]

Without knowing your particular machines, it is hard to make any specific recommendations. I can say that the errors you got above are first the timeout from this module just waiting for Node.js to say there was data and the second one was Node.js itself saying that it took too long to just open the TCP connection, which would indicate complete packet loss between the two machines (typically would be a firewall rule set to drop those packets).

[Alex-Pqn]

Okay very well, I will then inquire with my host, see the different options related to the firewall, by finding the problem. I'll be back here (if it doesn't bother) as a last resort to share more information about my hosting so maybe someone can help me a little more.

Thank you very much and have a good day :)