• 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!
  • 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 Nginx stopping each day, at same time

Gabor H

Basic Pleskian
Hi,

Having issue with Nginx. Websites on the server giving 502 Bad Gateway issue each day, nearly similar time at early morning.
Nginx is up and running. Status is green, enabled.
When I check the error log, I see only these kind of errors. (my IP masked)

2016/09/21 07:41:19 [error] 22856#0: *41591 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.76.81, server: , request: "GET /hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html HTTP/1.1", upstream: "http://XX.X.XXX.XXX:7080/hundewelt/5013350-trixie-sicherheits-adressanhanger-4-cm-4011905013350.html", host: "pfoetchenshop.eu"

Got a new server almost a week ago, with new IP. These GET's could be related to the previous owner of the IP.
But why is Nginx giving the 502 issue only early mornings? Any idea?
 
Hi Gabor,
check out this kb article...

https://kb.plesk.com/en/128431

  • For Debian based systems:

    Replace 'apache2 reload' with 'apache2 restart' in /etc/logrotate.d/apache2 file.

  • For RHEL based systems

    Replace 'httpd reload' with 'httpd restart' in /etc/logrotate.d/httpd file.

I hope that helps.
Kind regards

Lloyd
 
UPDATE>

Strange things happening here. Found out that in httpdocs the nginx configuration file for WP is gone, and a .htaccess is generated.
And the 502 issue is came in because in Hosting Settings I've set FPM served by Nginx.
(if I change it to FPM served by Apache, then 502 issue is gone)

So, the big question is, that why Nginx configuration file disappeared by the night from httpdocs?
 
Hi Lloyd,

Why is it necessary to do anything with Apache setting, if I've set FPM served by Nginx?

And pls see a kind of anomaly written above.

Regards,
Gabor.



Hi Gabor,
check out this kb article...

https://kb.plesk.com/en/128431

  • For Debian based systems:

    Replace 'apache2 reload' with 'apache2 restart' in /etc/logrotate.d/apache2 file.

  • For RHEL based systems

    Replace 'httpd reload' with 'httpd restart' in /etc/logrotate.d/httpd file.

I hope that helps.
Kind regards

Lloyd
 
onnect() failed (111: Connection refused) while connecting to upstream

Indicates that Apache is down.
I'm not sure what you mean by "Nginx configuration file disappeared by the night from httpdocs"?
There is no Nginx configuration file equivilent to .htaccess.

Regards

Lloyd
 
Ok, I'll look around again what's happening there.

Anyway, apache is needed to run and config anything related to apache, when Nginx is used
and FPM application served by Nginx?



Indicates that Apache is down.
I'm not sure what you mean by "Nginx configuration file disappeared by the night from httpdocs"?
There is no Nginx configuration file equivilent to .htaccess.

Regards

Lloyd
 
Hi Gabor,
yes exactly, even if one site is using Nginx-FPM, other things like File Sharing and Webmail need Apache and FastCGI.
Once you have made that modification I suggested, let me know tomorrow if you have the same problem.
Hope it helps
Kind regards

Lloyd
 
Back
Top