Docker hangs for a few minutes then fails with connect ETIMEDOUT
See original GitHub issueI just started to run this on my new ScaleWay server (Debian) and I noticed that it hands for a few minutes either at Checking free games for <email>
or Purchasing <Game>
and I don’t understand why since it worked very well before I change my distro on scaleway.
I don’t know if this is related to the app or the vps but maybe someone knows an answer or a new option to set a timeout if possible could be a help.
Thanks.
Here’s the full error:
[2021-06-03 22:55:08.623 +0300] ERROR (RequestError/18 on 5cd824e032d8): connect ETIMEDOUT 34.196.170.8:443
RequestError: connect ETIMEDOUT 34.196.170.8:443
at ClientRequest.<anonymous> (/usr/app/node_modules/got/dist/source/core/index.js:792:25)
at Object.onceWrapper (node:events:476:26)
at ClientRequest.emit (node:events:381:22)
at ClientRequest.origin.emit (/usr/app/node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)
at TLSSocket.socketErrorListener (node:_http_client:472:9)
at TLSSocket.emit (node:events:369:20)
at emitErrorNT (node:internal/streams/destroy:188:8)
at emitErrorCloseNT (node:internal/streams/destroy:153:3)
at processTicksAndRejections (node:internal/process/task_queues:81:21)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1138:16)
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Docker unresponsive after few minutes. Stopping Planning ...
When we try to stop containers through Powershell, the whole shutdown process hangs eventually. Even basic Docker commands are not responding.
Read more >connect ECONNREFUSED 127.0.0.1:5000 or Error: socket ...
The problem is in the CMD command in Dockerfile. From Docker docs: ... You need to provide the --host argument and change the...
Read more >Run your image as a container - Docker Documentation
Let's start our image and make sure it is running correctly. Execute the following command in your terminal. $ docker run node-docker.
Read more >[Solved] Npm install hung or takes too long time
Mostly (and for me as well) this error is due to incorrect proxy settings. Verify network proxy settings are correct. Else try removing...
Read more >Troubleshoot Lambda function retry and timeout issues ... - AWS
Resolution. Log the API calls made by the AWS SDK. Use Amazon CloudWatch Logs to get details about failed connections and the number...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think Epic has some sort of AWS WAF bot control policy configured that doesn’t like the direct HTTP calls. I see a similar timeout when running on a PIA VPN. But when using a browser, I can still load the homepage.
In your case, a programmatic timeout wouldn’t exactly work because it would still have the same VPS instance. I think the second time you tried, it got a new IP that the WAF wasn’t as eager to block.
I actually figured out what was causing issues when connecting via my VPN. It turns out my VPN was configured for a lower MTU value than my other network interfaces, which led to WSL2 failing all connections over the VPN. I just had to configure WSL2 to use a lower MTU value and the requests started working again.