• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Problem ERR_CONNECTION_REFUSED

NothernPeak

Basic Pleskian
Hi,

Please can you help me:

I have CentOS 6.5 and Plesk 12.0.18 Update #65.

Suddenly today all my websites on my VPS have stopped the work. In the browser I see the error:
ERR_CONNECTION_REFUSED when I try to open any of my website.

Plesk Panel is working.
Email services are working fine.
FTP is working.

I tried suggestions #12, #14 from this thread but they didn't help. File /plesk.conf seems to be correct.

I will glad for any help, please!

P.S. My VPS is on OVH and I can't submit a support ticket here, because my license key is not accepted.
 
Hi NothernPeak,

first, please don't mix the Plesk Control Panel ( with it's very own webserver "sw-cp-server" ) with your webserver(s) apache ( and nginx, if in use ) for your domains!

As you stated:
Plesk Panel is working.
... so please ignore work-arounds / solutions for "sw-cp-server". The mentioned thread is absolute useless for you, if your errors/issues are with apache ( + nginx, if in use ) and not with your Plesk Control Panel ( "sw-cp-server" ).


The very first step when you experience issues with your webserver(s) is always to restart the services. Please post errors/issues/problems when you restart the webserver(s) ( apache and/or nginx ) and try to include error - logs, so that investigations could be made. You find all commands, configuration - file and log - file - locations here:



Please make sure, that no firewall or iptables - setting are blocking the webserver(s) ports. You find a list of necessary open ports, when you use Plesk, here:

Please check as well, that Fail2Ban isn't blocking your current IP for some reason, if you use Fail2Ban. You could always restart Fail2Ban with the command "service fail2ban restart", which will flush ( flush = deletion of existing bans ) the iptables rules set by Fail2Ban.


In addition, you can always check with "netstat", if your webserver(s) are listening to your configured ports:

netstat -ntpl | grep httpd
( on some other systems than CentOS/RHEL) netstat -ntpl | grep apache2
netstat -ntpl | grep nginx
 
Hi UFHH01,

Many thanks for your reply!

I checked Plesk Panel > Server > Services:
[x] Web Server (Apache)
[x] Reverse Proxy Server (nginx)
[ ] IP Address Banning (Fail2ban) // NOT CHECKED

1. NGINX:

[root@vpsxxxxx 0]# /etc/init.d/nginx restart
Not starting nginx as it is disabled in config

Log files are empty:
/var/log/nginx/error.log
/var/log/nginx/access.log
/var/www/vhosts/<domain>/logs/proxy_access*_log

2. Apache:

I successfully stopped and started the service:

/var/log/httpd/access_log is empty

I attach error_log and error_log-20150920 (in apache.zip file)

/var/www/vhosts/<domain>/logs/access_log is empty
/var/www/vhosts/<domain>/logs/error_log is is old (last changes by yesterday and nothing suspicious, only records regarding wordpress)


3. [root@vpsxxxxx logs]# service fail2ban restart
fail2ban: unrecognized service


4. [root@vpsxxxxx logs]# netstat -ntpl | grep httpd
tcp 0 0 :::7080 :::* LISTEN 13915/httpd
tcp 0 0 :::7081 :::* LISTEN 13915/httpd

[root@vpsxxxxx logs]# netstat -ntpl | grep nginx?
[root@vpsxxxxx logs]#


5. Regarding ports. Where I can see a list of openning ports?

Please can you give more advices? Or can I give you access to my VPS server?

Thanks!
 

Attachments

  • apache.zip
    2.8 KB · Views: 6
Hi UFHH01,

Many thanks for your reply!

I checked Plesk Panel > Server > Services:
[x] Web Server (Apache)
[x] Reverse Proxy Server (nginx)
[ ] IP Address Banning (Fail2ban) // NOT CHECKED

1. NGINX:

[root@vpsxxxxx 0]# /etc/init.d/nginx restart
Not starting nginx as it is disabled in config

Log files are empty:
/var/log/nginx/error.log
/var/log/nginx/access.log
/var/www/vhosts/<domain>/logs/proxy_access*_log

2. Apache:

I successfully stopped and started the service:

/var/log/httpd/access_log is empty

I attach error_log and error_log-20150920 (in apache.zip file)

/var/www/vhosts/<domain>/logs/access_log is empty
/var/www/vhosts/<domain>/logs/error_log is is old (last changes by yesterday and nothing suspicious, only records regarding wordpress)


3. [root@vpsxxxxx logs]# service fail2ban restart
fail2ban: unrecognized service


4. [root@vpsxxxxx logs]# netstat -ntpl | grep httpd
tcp 0 0 :::7080 :::* LISTEN 13915/httpd
tcp 0 0 :::7081 :::* LISTEN 13915/httpd

[root@vpsxxxxx logs]# netstat -ntpl | grep nginx?
[root@vpsxxxxx logs]#


5. Regarding ports. Where I can see a list of openning ports?

Please can you give more advices? Or can I give you access to my VPS server?

Thanks!

Hi NothernPeak,
I found a strange behaviour in Nginx whit the last update, the #MU65
Maybe this can help: try restarting the Inverse proxy service (nginx) using Plesk under Server -> Services.

Let me know!
 

Attachments

  • Services.JPG
    Services.JPG
    60.7 KB · Views: 5
Hi NothernPeak,

1. NGINX:

[root@vpsxxxxx 0]# /etc/init.d/nginx restart
Not starting nginx as it is disabled in config

Log files are empty:
/var/log/nginx/error.log
/var/log/nginx/access.log
/var/www/vhosts/<domain>/logs/proxy_access*_log

It is really necessary, that you understand outputs from your commands, NothernPeak, to solve issues. Your output states clear, that nginx is disabled in your configuration file. To enable nginx please use the command:

/usr/local/psa/admin/bin/nginxmng --enable

Afterwards, to reconfigure your domain configuration files and all server configuration files, please use the command:

/usr/local/psa/admin/sbin/httpdmng --reconfigure-all


With the reconfiguration process, your webserver(s) should be restarted as well, so please check again with netstat, that apache and nginx are running and listening.


5. Regarding ports. Where I can see a list of openning ports?

Please can you give more advices? Or can I give you access to my VPS server?

If you would like to have custom, individual support, consider to open a support - ticket at Odin support. You find such necessary informations at:


If you don't have a firewall configured on your server, then your necessary ports are open on your server. You can check whether a port is open or not, with for example:

nmap -sS -O 127.0.0.1

netstat -nap


 
UFHH01,
Wulpi,

Thanks for your suggestions! My skills in configuration of the server are small.

I decided to re-install my VPS and recover websites from the Plesk backups. It solved my problem.

Earlier: CentOS 6.5 Plesk 12.0.8 Update 65
New VPS: CentOS 6.7 Plesk 12.0.8 Update 65.

Everything works fine now.
 
Back
Top