Can't access WHM interface after cPanel update and websites returning 503 error
Hi everyone, Last night I logged into my WHM and updated both cpanel and litespeed to their latest version. Every thing went fine and I rebooted the server and started developing my website. But when this morning I tried to log into cpanel again, I faced whit a Timed_Out browser error. I couldn't access neither of 2087 or 2083 ports. I opened multiple websites hosted on this server and all returned with 503 error page of litespeed. I could access it via SSH but after logging in I got this broadcast message:
I executed a reboot command which caused my websites to come live again but I still cant access my cPanel or WHM interface. This is my setup information:
Moderator Note: The original post was edited to replace a real domain name with removed-domain.tld.
Broadcast message from systemd-journald@ext-one.removed-domain.tld (Sun 2019-03-24 12:46:28 +0430):
dracut[6260]: Could not store the current command line parameters
Message from syslogd@ext-one at Mar 24 12:46:28 ...
dracut:Could not store the current command line parametersI executed a reboot command which caused my websites to come live again but I still cant access my cPanel or WHM interface. This is my setup information:
/etc/redhat-release:CentOS Linux release 7.6.1810 (Core)
/usr/local/cpanel/version:11.76.0.20
/var/cpanel/envtype:vmware
CPANEL=release
Litespeed version: 3.5.7Moderator Note: The original post was edited to replace a real domain name with removed-domain.tld.
-
Hi @Kiavash Rostami I'm wondering if somehow you triggered cPhulk's Brute force protection. You might want to take a look at the documentation here: cPHulk Management on the Command Line - cPanel Knowledge Base - cPanel Documentation and whitelist your IP and/or temporarily disable cPHulk to see if you're able to access cPanel/WHM once more. Thanks! 0 -
I'm facing the exact same issue.. I rebooted my server today after the update and can't access the WHM/cPanel interface since then. I can access the ssh. I also tried with whitelisted IPs but same result. Please help. 0 -
Whitelisted the ip address in cphulk? 0 -
You may try temporarily disabling cPHulkd and flushing the iptables rules (also temporarily) to determine if this is in fact the issue. 0
Please sign in to leave a comment.
Comments
4 comments