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

Zicane

Basic Pleskian
Hi, I have a huge problem.
Randomly, the website that I have on a Centos Server (with Plesk) go to unreachable, like 1 time daily.
While the Plesk panel and the server keep being reachable.
The only thing I can do for reach the website again is restart the entire server.
I have checked systems logs (messages) and there is nothing but only an errore of php-fpm that tells me "Php-fpm7.0 starts to fail", but I use Php 7.1.
I tried to see nginx logs and there is this:
" [error] 4465#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client:myserverip, server: , request: "GET / HTTP/1.1", upstream: "http://myserverip:7080/", host: "myserverip""


Where I can read other logs? Because in these logs, in the period of time of "unreachablity" there are no errors that helps me to find the problem.
Someone had the same problem?
Please help.
 
PHP 7.0 won't start if there are not websites using it, because in this case configuration files are missing for PHP 7.0. So if you are using PHP 7.1, it is correct that PHP 7.0 does not start. So this is a different problem from what your post is about.

There can be many reasons for the "connection refused while connecting to upstream" message. The message means that Nginx cannot receive an answer from Apache. The places to further look for the cause are
- Apache web server (Is it up and running at that time?)
- PHP-FPM service (Is it up and running at that time? Does it have enough resources, e.g. can it create further children or create new instances? How many instances is it using at the time of the error?)
- The website itself (Can you open a phpinfo(); page, so might the issue be caused by an infinite redirect? Does your script depend on input from other scripts that don't respond, e.g. external resources? Etc., endless possibilities there ...)
 
That's an interesting approach to "solve" it (turning Apache off completely ...). Yes, sure that will work, but then you cannot use Apache and the .htaccess file capability any longer, because all web requests will only be processed by Nginx.
 
Back
Top