On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Domains periodically unavailable for some time: (111: Connection refused) while connecting to upstream

Avatar
Vladimir Chernikov
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

  • The following errors can be found at Domains > example.com > Logs:

    CONFIG_TEXT: [error] 15231#0: *12218 connect() failed (111: Connection refused) while connecting to upstream, client: 203.0.113.2, server: example.com, request: "GET / HTTP/1.1", upstream: "https://192.0.2.2:7081/", host: "www.example.com"

  • Apache graceful restart was enabled according the article How to enable/disable graceful restart for Apache? but errors are still appeared.

  • Apache graceful restart takes few seconds before the new master process is deployed as can be seen in /var/log/apache2/error_log or /var/log/httpd/error_log:

    CONFIG_TEXT: [mpm_prefork:notice] [pid 11522] AH00170: caught SIGWINCH, shutting down gracefully
    [mpm_prefork:notice] [pid 16650] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips Apache mod_fcgid/2.3.9 configured -- resuming normal operations

Cause

When a subscription/domain is created Plesk restarts Apache and it causes a temporary downtime of Apache. 

Resolution

Configure Nginx to process all website's content:

  1. Log into Plesk
  2. Navigate to Domains > example.com > Apache & nginx Settings and disable Proxy mode

Warning: If Proxy mode is disabled, Apache rewrite rules and .htaccess files will not be processed. Apache still needs to be installed and running on a server.

Additional information

Apache restart interval configured in Plesk is ignored

Apache restarts frequently on Plesk running server: Caught SIGTERM, shutting down

Comments

3 comments

Sort by Date Votes
  • Avatar
    Andy Little

    It looks like it was Fail2ban adding my server IP that caused this issue for me. I tried the steps in this article but httpd would not restart. I had to run Plesk Repair to fix it.

    Hope this helps someone else!

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Andy,

    Thank you for sharing.

    It may be helpful to other Pleskians.

    0
    Comment actions Permalink
  • Avatar
    Claus Siebeneicher

    Had 502 Bad Gateway and this nginx error in the logs: 

    671#0: *1 connect() failed (111: Connection refused) while connecting to upstream

    Serving IPV4 and V6 and fail2ban running. Restarting fail2ban and setting the own IPs as trusted IP solved the issue. 

    		        

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles