If your websites hosted on Plesk are down after a server update or reboot, and you're encountering an ERR_CONNECTION_REFUSED error, don't worry! This guide will help you troubleshoot and resolve the issue.
Understanding the Issue
This error typically means that your server is refusing connections. In this case, it's likely due to a conflict between the Plesk Firewall and the Firewalld service. Both of these services use the iptables utility to manage network traffic, and having them both active can lead to connectivity issues.
Prerequisites
- Access to your server via SSH.
- Basic understanding of terminal commands.
Step 1: Connect to Your Plesk Server
Start by connecting to your server using SSH:
ssh username@$server-ipStep 2: Check Firewall Status
To confirm that the Firewalld service is running, you can check its status with the following command:
systemctl status firewalldStep 3: Stop and Disable Firewalld
If Firewalld is active, you should stop and disable it to avoid conflicts with the Plesk Firewall:
sudo systemctl stop firewalld && sudo systemctl disable firewalldStep 4: Verify Website Accessibility
After stopping Firewalld, check if your websites are now accessible. Open a web browser and try accessing your sites again.
Troubleshooting Tips
If your websites are still down, consider the following:
- Ensure that the Plesk Firewall is enabled and properly configured.
- Check the server logs for any error messages related to network services.
- Restart the Plesk service to refresh configurations:
sudo systemctl restart psaDisclaimer
Always test changes in a development environment before applying them to your production server. For the latest documentation and support, refer to the official Plesk resources.
