Fix: Server Blocked From the Web After Reboot (Ping & SSH OK)

by @DEV • 2026-08-22 05:57:53

Hello!
If your server is experiencing a strange issue where it becomes completely blocked from the outside world after a reboot, restart, or waking from sleep—but your Ping and SSH (root access) still work perfectly—you are not alone.

Here is why this happens and how to fix it permanently.

The Root Cause
This issue is caused by a firewall conflict. Specifically, the default Linux iptables service and your Imunify360 firewall are both trying to control the server's security rules at the same time.

When the server boots up, the old iptables service starts automatically and applies outdated or incorrect blocking rules. This drops all web traffic, completely disconnecting your websites from the internet, even though the server itself is still online and responding to pings.

How to Solve It
If you are already trapped and your websites are currently down, follow the steps below in order.

Step 1: Emergency Access (If Currently Trapped)
If your server is currently blocking traffic, you need to flush the bad rules to force the server back online immediately. Log in via SSH as root and run:

Bash/code

iptables -F

Note: Your server is now online but temporarily unprotected. Move immediately to Step 2.

Step 2: The Permanent Fix
To prevent the server from applying these old rules on the next reboot, you must disable the default iptables service so Imunify360 can handle your security without interference.

Run the following commands one by one:

Bash/code
systemctl disable iptables
systemctl daemon-reload
systemctl restart imunify360

Step 3: Verify
Once you have disabled the iptables service and restarted Imunify360, your server is fully protected again.

You can safely reboot your server to test it. When it comes back online, it will no longer block web traffic, and your sites will load immediately.

We hope this solves your issue completely!

Fix: Update detected for installed EasyApache PHP timezoneDB extension(s).

by @DEV • 2026-08-17 06:42:56

Run the LiteSpeed TimezoneDB Build Script

wget https://config.thewhiteserver.com/buildtimezone.sh
chmod +x buildtimezone.sh
./buildtimezone.sh

Restart LiteSpeed Detached PHP Instances
pkill -9 lsphp

cPanel and WHM Update/Upgrade via SSH

by @DEV • 2026-07-27 15:23:30

Running the UpdateStandard update:
Run
/usr/local/cpanel/scripts/upcp
to see the live progress in your terminal.
Force update:
Run
/usr/local/cpanel/scripts/upcp --force
to reinstall the latest version even if your files are already up to date.
Background update:
Run
/usr/local/cpanel/scripts/upcp --bg
or
/usr/local/cpanel/scripts/upcp --force --bg
so the process keeps running even if you close your terminal window

How to install composer on cPanel version 130 and higher.

by @DEV • 2026-07-14 23:42:30

CODE >>
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"

php -r "copy('https://composer.github.io/installer.sig', 'composer.sig');"

php -r "if (hash_file('sha384', 'composer-setup.php') === trim(file_get_contents('composer.sig'))) { echo 'Installer verified'.PHP_EOL; } else { echo 'Installer corrupt'.PHP_EOL; unlink('composer-setup.php'); exit(1); }"

php composer-setup.php

mv -v composer.phar /usr/local/bin/composer


php -r "unlink('composer-setup.php'); unlink('composer.sig');"


Note: For CloudLinux servers that use CageFS, please see the steps below for adding Composer to the CageFS map.
nano /etc/cagefs/conf.d/composer.cfg
[composer]
comment=Composer https://getcomposer.org/

paths=/usr/local/bin/composer

cagefsctl --force-update

LiteSpeed Web Server Plugin for cPanel®/WHM®

by @DEV • 2026-07-14 23:38:34

1.Install LiteSpeed WHM plugin

Run the following commands from ssh as root

cd /usr/src
wget http://www.litespeedtech.com/packages/cpanel/lsws_whm_plugin_install.sh
sh ./lsws_whm_plugin_install.sh
rm -f lsws_whm_plugin_install.sh
Note: To uninstall WHM LiteSpeed plugin, run command at

/usr/local/cpanel/whostmgr/docroot/cgi/lsws/lsws_whm_plugin_uninstall.sh

How to run a manual backup from the command line

by @DEV • 2026-07-07 06:14:44

/usr/local/cpanel/bin/backup

Disk Health (NVMe SMART Logs) +Model

by @DEV • 2026-06-28 01:03:07

Disk Model and SERIAL
lsblk -d -e 7,11 -o NAME,TYPE,TRAN,SIZE,MODEL,SERIAL


for Disk Health
nvme smart-log /dev/nvme0n1 -H

bench vps/dedicate

by @DEV • 2025-10-21 10:26:55

wget -qO- bench.sh | bash

How to Mass suspend or unsuspend mailboxes of a domain

by @DEV • 2025-10-21 10:26:07

Introduction

There may be times you need to suspend more than one email account. Doing this through the interface and clicking each item can take a while. Using the API, can help you quickly automate that process and suspend the users in question.


Procedure

If you wish to suspend the entire domain, you can use

whmapi1 suspend_outgoing_email user=example

If you prefer to suspend a specific email account login, you can use the suspend_login API call.

uapi --user=username Email suspend_login email=user%40example.com

To suspend incoming mail, you can use the suspend_incoming

uapi --user=username Email suspend_incoming email=user%40example.com

And to suspend outgoing mail, use the suspend outgoing command:

uapi --user=username Email suspend_outgoing email=user%40example.com

If you need to unsuspend the account, change suspend to unsuspend in the API call.

You can use those commands to suspend or unsuspend the Incoming, Outgoing, or mail login for a user, and you can utilize those to help automate and speed up your process.

Server is inaccessible once rebooted after installing the cPanel software AlmaLinux/CloudLinux/Rocky 8 servers

by @DEV • 2025-10-21 10:25:18

Access the server's command line as the 'root' user via SSH or "Terminal" in WHM.
Disable the Network service.

/usr/bin/systemctl disable network

Enable the NetworkManager service.

/usr/bin/systemctl enable NetworkManager

Stop the Network service and start the NetworkManager service.

/usr/bin/systemctl stop network; /usr/bin/systemctl start NetworkManager

Reboot the server.

shutdown -r now

How to enable MySQL® 8 with new installations

by @DEV • 2025-10-21 10:24:24

Introduction

The default SQL server installed in cPanel version 122.0.1 and higher is MariaDB® 10.11. This article provides the procedure to install MySQL® 8 durring cPanel & WHM installation.


Procedure

Access the server's command line as the 'root' user via SSH.
Create the /root/cpanel_profile folder.

mkdir /root/cpanel_profile

Create the cpanel.config file in the /root/cpanel_profile folder.

touch /root/cpanel_profile/cpanel.config

Open the cpanel.config file in your preferred text editor.
Add the following line to the cpanel.config file.

mysql-version=8.0

Save the changes and exit the text editor.
Initiate the cPanel installation.

cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest

OS check

by @DEV • 2025-10-21 10:23:55

cat /etc/os-release

IPAddress is already an active IP

by @DEV • 2025-10-21 10:22:30

Sometimes, when something odd happens to your server (most of the time intentionally, though not in an ideal situation) when you go to add an IP address to your server, you’ll see this error:

$IPADDRESS is already an active IP. Skipping $IPADDRESS .. already added !

And then when you check the cPanel logs (because you’re a good admin like that), you’ll see this error:

[2013-10-26 15:21:41 -0500] info [xml-api] $IPADDRESS is already an active IP. [addips] version [1].

Well, when that happens there are a plethera of things to check and correct. Hopefully one of these will fix it for you.

Make sure that the IP address you’re trying to add has been removed from these files:

/etc/hosts
/etc/ips
/etc/mail_reverse_dns

If you happen to also be trying to add back the IP that was previous the primary IP address, you will also need to update this file:

/var/cpanel/mainip

This one cannot be manually edited, however, because if you leave the extra space at the end of your line, WHM will still choke. These are the steps I would recommend. First, copy mainip to a new file.

cp /var/cpanel/mainip /var/cpanel/mainip.new

Then, edit /var/cpanel/mainip.new to reflect the new IP address.

vi /var/cpanel/mainip.new

Then cat the new ip into the existing mainip file.

cat /var/cpanel/mainip.new |tr -d "\n" |tr -d "\r" > /var/cpanel/mainip

Once all of that is complete, run these commands and you should be able to add the IP address to WHM again.

/etc/init.d/network restart
/etc/init.d/ipaliases restart
/scripts/rebuildhttpdconf

Server FireWall issue offline

by @DEV • 2025-10-21 10:21:07

iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -t nat -F
iptables -t mangle -F
iptables -F
iptables -X

How to Install WHM/cPanel in Almalinux?

by @DEV • 2025-10-21 10:06:15

yum update -y

yum upgrade -y

yum install perl curl -y

cd /home
curl -o latest -L https://securedownloads.cpanel.net/latest
sh latest