Sporadic cURL error 28: Resolving timed out after 5000 milliseconds #761
nine-2-five
started this conversation in
General
Replies: 1 comment
-
I had this issue, it was caused by the container not being able to properly resolve to itself via my nginx revese proxy the fix was to add the extra_hosts directive to the yaml for the container as so.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm using WordPress FPM 8.0 with the official NGINX image as a reverse proxy. I'm getting cURL error 28: Resolving timed out after 5000 milliseconds, sporadically, on pages that use wp_remote_post to get data from an Express.js API in the same datacenter (but different domain). The proxy I believe can be excluded from this problem, because the same error was logged with Open LiteSpeed proxy also.
The wp_remote_post gets the data 99% of the time, but I'd still like to know why this error happens 10-20 times a day.
Also, I had the chance to call the API using Postman within seconds of error being logged, and it responded within 100ms on each call I made.
Beta Was this translation helpful? Give feedback.
All reactions