Stuck with the error, err_connection_refused in Plesk? We can help you.

As part of our Server Management Services, we assist our customers with several Plesk queries.

Today, let us see how our techs fix this error for our customers.

err_connection_refused Plesk

Most often, we receive the error: err_connection_refused when we access the Plesk panel, due to some issue with the configuration files.

Moving ahead, let us see how our Support Techs fix this error.

• Solution 1

1. Initially we log in to the server via SSH
2. Then we change the user to root
3. Later, we run the following commands on the terminal:

# plesk repair all

or

# plesk repair installation

• Solution 2

In case the first didn’t work, we check the status of the server apache.

We need to check if it gives an error like this:

Loaded: loaded (/lib/systemd/system/apache2.service; enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─forking.conf
Active: failed (Result: exit-code) since Thu 2021-06-24 13:28:57 CEST; 56s ago
Process: 12279 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

Jun 24 13:28:57 ocr-immowiin systemd[1]: Starting LSB: Apache2 web server…
Jun 24 13:28:57 ocr-immowiin apache2[12279]: Starting web server: apache2 failed!
Jun 24 13:28:57 ocr-immowiin apache2[12279]: The apache2 configtest failed. … (warning).
Jun 24 13:28:57 ocr-immowiin apache2[12279]: Output of config test was:
Jun 24 13:28:57 ocr-immowiin apache2[12279]: apache2: Syntax error on line 216 of /etc/apache2/apache2.conf: Syntax error on line 5 of /etc/apache2/conf-enabled/zz010_psa_httpd.conf: Syntax error on line…
Jun 24 13:28:57 ocr-immowiin apache2[12279]: Action ‘configtest’ failed.
Jun 24 13:28:57 ocr-immowiin apache2[12279]: The Apache error log may have more information.
Jun 24 13:28:57 ocr-immowiin systemd[1]: apache2.service: control process exited, code=exited status=1
Jun 24 13:28:57 ocr-immowiin systemd[1]: Failed to start LSB: Apache2 web server.
Jun 24 13:28:57 ocr-immowiin systemd[1]: Unit apache2.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

In that case,

1. First, we connect to the server using SSH

2. Then we change to user root

3. We then replace updated version of the file, PhysicalHosting.php to /usr/local/psa/admin/plib/Template/Variable/Domain/:

# wget https://plesk.zendesk.com/hc/article_attachments/4407408199954/PPPM-13232.tgz && tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/

4. Eventually, we rebuild the webserver configuration files:

# plesk sbin httpdmng –reconfigure-all

• Solution 3

On the other hand, if the Plesk is Plesk onyx version then, we check the status of the service, sw-cp-server.

However, if it fails, we try to restart it.

# service sw-cp-server restart

sw-cp-serverd: nginx: [emerg] “ssl_ciphers” directive is duplicate in /etc/sw-cp-server/conf.d/ssl.conf:1
sw-cp-serverd: nginx: configuration file /etc/sw-cp-server/config test failed

During the restart, if we come across the above error, it is a software issue with internal # PPPM-3228

In order to fix this, we remove /etc/sw-cp-server/conf.d/ssl.conf file and restart sw-cp-server service:

# rm -f /etc/sw-cp-server/conf.d/ssl.conf
# service sw-cp-server restart

[Stuck with it still? We are available 24*7 for you]

Conclusion

In short, we saw how our Support Techs fix the Plesk error for our customers.