• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue connect() failed (111: Connection refused) while connecting to upstream

Azurel

Azurel

Silver Pleskian
I get very often this errors in proxy_error.log:

[error] 19343#0: *2462301 connect() failed (111: Connection refused) while connecting to upstream, client: xxxx
[error] 19875#0: *2462746 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxxx


CentOS Linux 7.3.1611 (Core)‬
Product Plesk Onyx Version 17.0.17 Update #18
Server version: Apache/2.4.6 (CentOS) built: Nov 14 2016 18:04:44

What can I do to fix this?
 
You must log in or register to reply here.

Similar threads

C
Issue Plesk Premium Email Autodiscover.xml 502 Bad Gateway 18.0.71 Update 2
Replies
3
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
A
Issue Angular SSR on Plesk 502 Bad Gateway error
Replies
0
Views
5K
Aapklub
A
I
Issue 502 error Node and Angular SSR
Replies
2
Views
6K
igorosabel
I
T
Resolved nginx/apache proxy issue on all domains and webmail / ubuntu 22.04 on arm / external ip instead of localhost
Replies
9
Views
7K
propz
propz
Mario Chamorro
Input Webmail 502 Bad Gateway
Replies
0
Views
10K
Mario Chamorro
Mario Chamorro
Back
Top