• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue 704710#0: *18394 upstream timed out (110: Connection timed out) while SSL handshaking to upstream

belugaed

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.54_build1800230824.08 os_Ubuntu 20.04
Hi,

Over the past week or so we've been getting the following errors across all our nginx sites, causing them to become unresponsive with 504 gateway timeouts. Restarting the nginx service brings them back.

We've checked that 127.0.0.1 and the server IPs are added to the Fail2Ban whitelist.

In the application firewall logs we have these errors at the same time:

failed to make connection to backend: httpd-UDS
18394 upstream timed out (110: Connection timed out) while SSL handshaking to upstream
704710#0: *18977 upstream timed out (110: Connection timed out) while connecting to upstream

nginx settings for one of the site's below. Server load is fine at the time of these errors.

We have however introduced a site that has had 386313Mb traffic in 18 days, bearing in mind the frontend is statically served externally and this just serves images and videos.... I suspect this might have an impact even from a bandwidth point of view potentially?

1695021701648.png
 
Hello, @belugaed!

Please have a look at this answer:

Looks like Apache cannot serve the files quickly.
 
Back
Top