• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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

B

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:

Resolved - nginx Fails, Bringing Site Down

Hi, We had a client's site go down, and investigation showed the issue to be with nginx. The log showed multiple entries like this: 3619#0: *22389 upstream timed out (110: Connection timed out) while SSL handshaking to upstream To get the site back up while troubleshooting, we tried to...
talk.plesk.com talk.plesk.com

Looks like Apache cannot serve the files quickly.
 
You must log in or register to reply here.

Similar threads

N
Question Site spamming headers, want to find out what it's doing.
Replies
5
Views
888
tessa67
tessa67
P
Issue Increase Nginx timeout
Replies
1
Views
5K
scsa20
scsa20
A
Issue Website sometime getting down due to nginx & apache error
Replies
3
Views
4K
arjch
A
Z
Issue Prestashop 8 : very slow and error "504 Gateway Time-out - Nginx"
Replies
1
Views
7K
1nghi
1
R
Resolved upstream timed out (110: Connection timed out) while connecting to upstream
2
Replies
24
Views
43K
rhand
R
Back
Top