• 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 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

A
Issue Website sometime getting down due to nginx & apache error
Replies
3
Views
339
arjch
A
Z
Issue Prestashop 8 : very slow and error "504 Gateway Time-out - Nginx"
Replies
1
Views
2K
1nghi
1
A
Question Which factors determine the maximumconcurrent users in Plesk?
Replies
1
Views
778
Ayki
A
R
Resolved upstream timed out (110: Connection timed out) while connecting to upstream
2
Replies
24
Views
23K
rhand
R
C
Issue Gateway timeout
Replies
3
Views
707
Bitpalast
Bitpalast
Back
Top