Can't login to Cyberpanel, but it's running

[TangoBravo]

Can’t log into Cyberpanel, but it’s running (the website is live)

Running on a Digital Ocean Droplet.
Can’t tell you what version but SSH console tells me “Cyberpanel is up to date”

Thinking that maybe DO updated Cyberpanel (they sent out an email saying I need to upgrade immediately) I didn’t at the time, was going to that today.

When I go to the IP_address:8443 (I am on cloudflare so 8090 is out)
I get:
ERR_CONNECTION_REFUSED

Trying to help myself, I searched and I think the problem was the firewall
I learned that cyberpanel uses firewalld.

Tried the commands to get it working but no love
systemctl status firewalld
First, I got the mask error so I unmasked it
systemctl unmask --now firewalld.service

Tried
sudo firewall-cmd --permanent --add-port=8443/tcp
Adding the port command didn’t work (forgot the error)

Now when I use:
systemctl status firewalld
I get “not running”

systemctl enable firewalld
systemctl start firewalld

I get
Nov 12 17:10:16 Cyberpanel1 systemd[1]: Starting firewalld - dynamic firewall daemon…
Nov 12 17:10:16 Cyberpanel1 systemd[1]: Started firewalld - dynamic firewall daemon.
Nov 12 17:10:28 Cyberpanel1 systemd[1]: firewalld.service: Deactivated successfully.

So no matter what I do, firewalld doesn’t stay running.
Even though it’s not running, I still can’t get into Cyberpanel.
(I checked, no firewall on DO btw).

What am I doing wrong? Even if get firewalld running, I still can’t get into Cyberpanel.

I hope I didn’t make it worse trying to figure it out on my own.

If anyone of you magicians (it what it seem like to me, I’m not kidding) can suggest what to do, please let me know.

[Ariyan]

You can follow this guide.

Those who Can't Access SSH and Still can't recover their Server!

Hello Hope everyone doing well. I have seen so many users still couldn’t recover their servers. NO Access to SSH ( Connection Refused or Timeout ) Unable to Access cyberpanel Unable to Access Litespeed Not able to Login to Server Console or Recovery Mode After analysing 100+ servers in such situations, I have found that the hacker modified the netplan, network files and that’s why the server OS couldn’t connect to the Internet itself and nothing works! There we can do these things to Initi…

[TangoBravo]

Not applicable to my issue.
but thanks anyway for the service offer.

[Ariyan]

Okay.

Do your SSH works. If yes then run theses commands.

systemctl status lscpd
systemctl restart lscpd

[TangoBravo]

Yes, SSH works and I now have firewalld running after a reboot.

I ran both of these:
sudo firewall-cmd --permanent --add-port=8443/tcp
sudo firewall-cmd --permanent --add-port=8090/tcp

And they were accepted.

Still can’t log into cyberpanel via
IPAddress:8443 or IPAddress:8090

Websites inside Cyberpanel still running.

Ran the suggested commands
systemctl status lscpd
systemctl restart lscpd

Got this:

Rebooted the droplet, now it coming back as:
● lscpd.service - LSCPD Daemon
Loaded: loaded (/etc/systemd/system/lscpd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-11-13 13:16:17 UTC; 35s ago
Process: 924 ExecStart=/usr/local/lscp/bin/lscpdctrl start (code=exited, status=0/SUCCESS)
Main PID: 1010 (lscpd)
CGroup: /system.slice/lscpd.service
├─1010 “lscpd (main)”
├─1011 “lscpd (lscgid)”
├─1016 “lscpd (#01)”
└─1020 /usr/local/CyberCP/bin/lswsgi -m /usr/local/CyberCP/CyberCP/wsgi.py

Nov 13 13:16:13 Cyberpanel1 systemd[1]: Starting LSCPD Daemon…
Nov 13 13:16:15 Cyberpanel1 lscpdctrl[924]: [OK] lscpd: pid=1010.
Nov 13 13:16:17 Cyberpanel1 systemd[1]: Started LSCPD Daemon.

Still can’t login to Cyberpanel.

[Ariyan]

did you restarted lscpd?

Or you can DM the IP I can check for it

[TangoBravo]

I figured it is a bad situation so before create a new droplet to replace this, I just ran the upgrade to see what, if anything happens.
It’s either going to work fine or it won’t.
Worse case scenario, I start a new droplet with new Cyberpanel and just upload the backup of my wordpress site…
I’ll update as to what happens…

Ok: updated Ubuntu, undated Cyberpanel, rebooted the droplet, rebooted Cyberpanel.
Sites are working, but I can’t login to Cyberpanel…
Checked firewalld again and it’s running and ports 8090 and 8043 are running.
No idea what to try next or even what the issue is.

Open to any ideas or else I’m going to have to spend another few hours creating another droplet…

How can it be that I can disable firewalld, clear my cache, try from another IP and I still can login into Cyberpanel???

I think I answered by own question. I’m thinking that it’s not cyberpanel or firewalld (else I could login with the firewall off right? but it’s digital ocean’s cloud fiirewall. They may have changed the port when they sent out a warning that cyberpanel had to be updated due to a security vulnerability.

will share the solution when I have it…

Another update:
It seems port 8443 is open in my cloud firewall in Digital Ocean
when I try
IP:8443
I get:
500 Server error
(this is after the cyberpanel and ubuntu upgrade.)

I guess I’m stuck in hosting hell…

What is the process to troubleshoot the 500 server error in cyberpanel?

[Ariyan]

@TangoBravo

500 Server error
(this is after the cyberpanel and ubuntu upgrade.)

Those who Can't Access SSH and Still can't recover their Server!

Hello Hope everyone doing well. I have seen so many users still couldn’t recover their servers. NO Access to SSH ( Connection Refused or Timeout ) Unable to Access cyberpanel Unable to Access Litespeed Not able to Login to Server Console or Recovery Mode After analysing 100+ servers in such situations, I have found that the hacker modified the netplan, network files and that’s why the server OS couldn’t connect to the Internet itself and nothing works! There we can do these things to Initi…

For this issue You can check the 2nd Step remove the Kingsing. If you have ssh access then try removing and then kill all the processes using too many resource. And then restart lsws and lscpd then reboot your system. You system should be perfect.

And I strongly believe the problem is because of the malware.

If you would love to explore you can try this otherwise if you have backup then restore it.