Arama Yap Mesaj Gönder
Biz Sizi Arayalım
+90
X
X

Wählen Sie Ihre Währung

Türk Lirası $ US Dollar Euro
X
X

Wählen Sie Ihre Währung

Türk Lirası $ US Dollar Euro

Wissensdatenbank

Startseite Wissensdatenbank Server/VPS/VDS Fixing cPanel Access Issues After R...

Bize Ulaşın

Konum Halkalı merkez mahallesi fatih cd ozgur apt no 46 , Küçükçekmece , İstanbul , 34303 , TR

Fixing cPanel Access Issues After Reboot on a VDS: Port Opening, Firewall & Network Configuration

Is your VDS becoming unreachable after installing cPanel and performing a reboot? This is a common issue caused by misconfigured firewall rules, missing port access, or improper network settings. In this article, we'll explain how to permanently fix cPanel access problems after reboot by correctly configuring ports, disabling unnecessary firewalls, and ensuring your network settings persist across reboots.


1. The Problem: Why Do You Lose Access After Installing cPanel?

When you install cPanel on a fresh VDS, the setup process might modify:

  • Network interface behavior (such as eth0, ens18, etc.)

  • Firewall configurations (firewalld, iptables)

  • SSH and cPanel-related port permissions

  • Cloud-specific routing or NAT settings

After a reboot, the server may lose connectivity because one or more of these configurations reset or block access.


2. Permanent Fix: Step-by-Step Solutions

2.1 Open Required Ports

Make sure all essential ports are open:

For firewalld:

firewall-cmd --permanent --add-port=22/tcp firewall-cmd --permanent --add-port=2087/tcp firewall-cmd --permanent --add-port=2083/tcp firewall-cmd --permanent --add-service=http firewall-cmd --permanent --add-service=https firewall-cmd --reload

For iptables:

iptables -I INPUT -p tcp --dport 22 -j ACCEPT iptables -I INPUT -p tcp --dport 2087 -j ACCEPT iptables -I INPUT -p tcp --dport 2083 -j ACCEPT service iptables save systemctl restart iptables

2.2 Make Network Configuration Persistent

Edit your network interface config (/etc/sysconfig/network-scripts/ifcfg-eth0 or similar):

NM_CONTROLLED=no ONBOOT=yes BOOTPROTO=static IPADDR=192.168.1.100 NETMASK=255.255.255.0 GATEWAY=192.168.1.1

Replace values with your hosting provider’s IP information.

Apply changes:

systemctl restart network

2.3 Disable NetworkManager (Optional)

In some cases, NetworkManager can override your network config after a reboot:

systemctl stop NetworkManager systemctl disable NetworkManager

3. Disabling firewalld (Temporary Solution)

If you're in a rush and can't configure ports correctly right now:

systemctl stop firewalld systemctl disable firewalld

Warning: This is not recommended for production servers. It’s better to open only the required ports instead of disabling your firewall entirely.


4. Additional Steps After cPanel Installation

  • License check: /usr/local/cpanel/cpkeyclt

  • Check if cPanel services are running: systemctl status cpanel

  • NAT configuration (if needed): WHM > Basic WebHost Manager Setup > Public/Private IP Mapping


Conclusion

Losing access to your VDS after installing cPanel and rebooting is usually caused by misconfigured firewall rules or non-persistent network settings. By following the steps above, you can ensure your VDS remains accessible and your cPanel stays operational—even after reboots.

Finden Sie nicht die Informationen, die Sie suchen?

Ticket erstellen
Fanden Sie es nützlich?
(11114 mal angesehen / 5343 Kunden fanden es hilfreich)

Call now to get more detailed information about our products and services.

Top