503 Service Unavailable on admin panel i.e. 8090 after server upgrade

503

Service Unavailable

The server is temporarily busy, try again later!

I just upgraded to Ubuntu 24 and now getting 503 error on admin panel. Please suggest next steps.

Is this still applicable - Error 503 Service Unavailable After Update

No reply to similar past issue - 503 Error facing after os upgradation and 503 Service Unavailable

Note: All websites are up, some more important notes.

  1. Server is on oracle cloud.
  2. 8090 was down without 503 error.
  3. I upgraded the server, it lead to overrides to some configs and I kept almost all of them to earlier configs.
  4. All sites were down, I added 80, 443 and 8090 to iptables.

Everything came back online but 8090 is 503 error.

Hello @shubhijain

Are you using cloudflare for DNS management ?

Thanks @josephgodwinke for reply. But I haven’t made any change in my cloudflare settings. It’s a A pointer and proxy status is DNS only.

Then it maybe any reason from the lscpd service is down or server is overloaded or firewall blocked your ip address. You can check by running:

$ systemctl status lscpd
$ systemctl status lsws

Run the following command to see if your IP is listed in the CSF deny list:

$ csf -g your_ip_address
# unblock your ip address if its in the deny list
$ csf -dr your_ip_address
# whitelist your ip address
$ echo "your-ip-address" >> /etc/csf/csf.allow
csf -r
# test config for possible issues with our recent changes
$ perl /etc/csf/csftest.pl

If the critical cyberpanel services are down you should restart them. You can also run the cyberpanel upgrade script to see if resolves the issue.

Thanks @josephgodwinke once again for quick revert. Sharing the log output:

● lscpd.service - LSCPD Daemon
     Loaded: loaded (/etc/systemd/system/lscpd.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-01-19 06:11:30 UTC; 2h 41min ago
    Process: 1044 ExecStart=/usr/local/lscp/bin/lscpdctrl start (code=exited, status=0/SUCCESS)
   Main PID: 1316
     CGroup: /system.slice/lscpd.service
             ├─1316 "lscpd (main)"
             ├─1319 "lscpd (lscgid)"
             └─1320 "lscpd (#01)"
Jan 19 06:11:23 cyberpanel-in-domain-in systemd[1]: Starting lscpd.service - LSCPD Daemon...
Jan 19 06:11:28 cyberpanel-in-domain-in lscpdctrl[1044]: [OK] lscpd: pid=1316.
Jan 19 06:11:30 cyberpanel-in-domain-in systemd[1]: Started lscpd.service - LSCPD Daemon.
ubuntu@cyberpanel-in-domain-in:~$ systemctl status lsws
● lshttpd.service - OpenLiteSpeed HTTP Server
     Loaded: loaded (/etc/systemd/system/lshttpd.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-01-19 06:11:29 UTC; 2h 41min ago
    Process: 1045 ExecStart=/usr/local/lsws/bin/lswsctrl start (code=exited, status=0/SUCCESS)
   Main PID: 1341
     CGroup: /system.slice/lshttpd.service
             ├─ 1341 "openlitespeed (lshttpd - main)"
             ├─ 1358 "openlitespeed (lscgid)"
             ├─ 1980 "openlitespeed (lshttpd - #01)"
             ├─ 1981 "openlitespeed (lshttpd - #02)"
             ├─29102 lsphp
             ├─29365 lsphp
             ├─29468 lsphp
             ├─29597 lsphp
             ├─29675 lsphp
             ├─29689 lsphp
             ├─29729 lsphp
             ├─29768 lsphp
             ├─29796 lsphp
             ├─29800 lsphp
             └─29801 lsphp
Jan 19 06:11:23 cyberpanel-in-domain-in systemd[1]: Starting lshttpd.service - OpenLiteSpeed HTTP Server...
Jan 19 06:11:27 cyberpanel-in-domain-in lswsctrl[1045]: [OK] litespeed: pid=1341.
Jan 19 06:11:29 cyberpanel-in-domain-in systemd[1]: Started lshttpd.service - OpenLiteSpeed HTTP Server.
ubuntu@cyberpanel-in-domain-in:~$ csf -g 106.219.123.133
Command 'csf' not found, did you mean:
  command 'cs' from deb csound (1:6.18.1+dfsg-1)
  command 'sf' from deb ruby-sprite-factory (1.7.1-4)
  command 'cst' from deb imx-code-signing-tool (3.3.2+dfsg-1)
  command 'csh' from deb csh (20230828-1)
  command 'csh' from deb tcsh (6.24.10-3)
  command 'csr' from deb rheolef (7.2-3build3)
  command 'caf' from deb libcoarrays-mpich-dev (2.10.1-1)
  command 'caf' from deb libcoarrays-openmpi-dev (2.10.1-1)
  command 'csc' from deb chicken-bin (5.3.0-1)
  command 'csi' from deb chicken-bin (5.3.0-1)
  command 'gsf' from deb libgsf-bin (1.14.51-2ubuntu0.1)
  command 'psf' from deb tcm (2.20+TSQD-7)
Try: sudo apt install <deb name>

I don’t think it is my ip that is blocked as I am opening for first time after obtaining new dynamic IP form my ISP (which is on every modem restart). I am using Oracle Cloud which blocks a lot of app installs, let me know if csf is mandatory for cyberpanel to work. I will attempt to bypass Oracle’s DNS server and see if I am able to install it then.

  1. cyberpanel can function without CSF, but its recommend to use a firewall like csf. As it enhances security by managing access and protecting against unauthorized connections.
  2. Since you mentioned using a dynamic ip address that changes with each modem restart, this should not typically cause blocking issues unless the previous ip address was flagged.
  3. As you stated attempting to bypass oracle dns server might help if you suspect dbns resolution issues are affecting your ability to use cyberpanel. You can switch to google dns(8.8.8.8) or cf dns (1.1.1.1) test and let us know.

@josephgodwinke what command should I run to ensure cyberpanel is updated perfectly? Is there any re-installation command which doesn’t impact the 30+ sites which are running currently on this server?

Upgrade from stable branch:

$ sh <(curl https://raw.githubusercontent.com/usmannasir/cyberpanel/stable/preUpgrade.sh || wget -O - https://raw.githubusercontent.com/usmannasir/cyberpanel/stable/preUpgrade.sh) &> /var/log/upgradeLogs.txt

Then check logs at /var/log/upgradeLogs.txt

Fetching latest data from CyberPanel server...
This may take few seconds...
Checking root privileges...
You are running as root...
Checking server location...
Unable to detect your system...
CyberPanel is supported on x86_64 based Ubuntu 18.04, Ubuntu 20.04, Ubuntu 20.10, Ubuntu 22.04, CentOS 7, CentOS 8, AlmaLinux 8, RockyLinux 8, CloudLinux 7, CloudLinux 8, openEuler 20.03, openEuler 22.03...
CyberPanel is supported on x86_64 based Ubuntu 18.04, Ubuntu 20.04, Ubuntu 20.10, Ubuntu 22.04, CentOS 7, CentOS 8, AlmaLinux 8, RockyLinux 8, CloudLinux 7, CloudLinux 8, openEuler 20.03, openEuler 22.03... [404]

Not sure if 404 is error here.

BTW, I had fixed DNS and was able to ping internet.

$ apt-get update
Hit:1 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
Hit:2 http://ap-mumbai-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports noble InRelease
Get:3 http://ap-mumbai-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports noble-updates InRelease [126 kB]
Hit:4 http://ap-mumbai-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports noble-backports InRelease
Fetched 126 kB in 6s (21.4 kB/s)
Reading package lists... Done
# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# do-release-upgrade
Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release
set Prompt=normal in /etc/update-manager/release-upgrades.

Any next steps?

BTW I did observe following error logs:

tail /usr/local/lscp/cyberpanel/logs/error.log

2025-01-25 08:54:32.002331 [NOTICE] [<IP>:5754] ExtConn timed out while processing.
2025-01-25 08:54:33.004921 [NOTICE] [<IP>:17254] ExtConn timed
out while processing.

What are these ports? Do I need to enable them for cyberpanel to work?

-- Boot f039c12944d54191ad21feefa5dcce5e --
Jan 25 08:11:36 cyberpanel-domain-in systemd[1]: Starting lscpd.service - LSCPD Daemon...
Jan 25 08:11:41 cyberpanel-domain-in lscpdctrl[1096]: [OK] lscpd: pid=1364.
Jan 25 08:11:43 cyberpanel-domain-in systemd[1]: Started lscpd.service - LSCPD Daemon.
Jan 25 08:25:25 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, s>
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: Stopping lscpd.service - LSCPD Daemon...
Jan 25 08:34:37 cyberpanel-domain-in lscpdctrl[6683]: [OK] lscpd: stopped.
Jan 25 07:55:51 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:57:58 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:57:59 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:58:06 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:58:07 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:58:08 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 07:58:10 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 08:02:18 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 08:09:27 cyberpanel-domain-in systemd[1]: Stopping lscpd.service - LSCPD Daemon...
Jan 25 08:09:28 cyberpanel-domain-in lscpdctrl[490216]: [OK] lscpd: stopped.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: lscpd.service: Deactivated successfully.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1316 (lscpd) remains running after unit stopped.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1319 (lscpd) remains running after unit stopped.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1320 (lscpd) remains running after unit stopped.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 301032 (lsphp) remains running after unit stopped.
Jan 25 08:09:28 cyberpanel-domain-in systemd[1]: Stopped lscpd.service - LSCPD Daemon.
-- Boot f039c12944d54191ad21feefa5dcce5e --
Jan 25 08:11:36 cyberpanel-domain-in systemd[1]: Starting lscpd.service - LSCPD Daemon...
Jan 25 08:11:41 cyberpanel-domain-in lscpdctrl[1096]: [OK] lscpd: pid=1364.
Jan 25 08:11:43 cyberpanel-domain-in systemd[1]: Started lscpd.service - LSCPD Daemon.
Jan 25 08:25:25 cyberpanel-domain-in systemd[1]: /etc/systemd/system/lscpd.service:11: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: Stopping lscpd.service - LSCPD Daemon...
Jan 25 08:34:37 cyberpanel-domain-in lscpdctrl[6683]: [OK] lscpd: stopped.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: lscpd.service: Deactivated successfully.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1364 (lscpd) remains running after unit stopped.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1367 (lscpd) remains running after unit stopped.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: lscpd.service: Unit process 1369 (lscpd) remains running after unit stopped.
Jan 25 08:34:37 cyberpanel-domain-in systemd[1]: Stopped lscpd.service - LSCPD Daemon.
-- Boot 93a4f9b8eb3345b894e7ce7d3b48e093 --
Jan 25 08:36:33 cyberpanel-domain-in systemd[1]: Starting lscpd.service - LSCPD Daemon...
Jan 25 08:36:38 cyberpanel-domain-in lscpdctrl[1116]: [OK] lscpd: pid=1375.
Jan 25 08:36:40 cyberpanel-domain-in systemd[1]: Started lscpd.service - LSCPD Daemon.

Cyberpanel still does not support Ubuntu 24, only Ubuntu 22 i believe, according to this: GitHub - usmannasir/cyberpanel: Cyber Panel - The hosting control panel for OpenLiteSpeed