• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Error : upstream timed out (110: Connection timed out) while reading response header from upstream

cipcip

Basic Pleskian
Server operating system version
Ubuntu 20.04 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.49.2
Hello ,
I am facing this error with my app written in Node.js and React . I have other React apps on the same server without any issues .
The only difference is that this app is communicating with Clicksend.com and I suspect that it is taking too long to receive a response from them ?!

The full error is :
2023/02/22 09:33:56 [error] 641517#0: *20358 upstream timed out (110: Connection timed out) while reading response header from upstream, client: client_IP_here, server: api.esanta.xyz, request: "POST /api/v1/order HTTP/2.0", upstream: "https://server_ip:7081/api/v1/order", host: "api.esanta.xyz", referrer: "Santa Postcard Express | eSanta.xyz"

I have tried to add the following NGINX directives to both api subdomain and domain:
proxy_connect_timeout 180s;
proxy_send_timeout 180s;
proxy_read_timeout 180s;
fastcgi_send_timeout 180s;
fastcgi_read_timeout 180s;

But nothing works ...
Do you have any suggestions for me ?

Thank you,
Cristian
 
As you already suspected, the error is caused by an unresponsive script. If no result is delivered to Nginx, it times out.
 
As you already suspected, the error is caused by an unresponsive script. If no result is delivered to Nginx, it times out.

Thank you for the quick answer . I got suspicious because I saw the port of 7081 in the logs at: https://server_ip:7081/api/v1/order
Is this the port that is used for communication between nginx and apache ?

Thank you,
Cristian
 
Back
Top