• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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