CyberPanel Community

Subject: 503 Error: Upgrade/Install fails at WSGI-LSAPI step (404 Not Found)

dd
ddegner #1

Hello CyberPanel Community,

I am experiencing a persistent “503 Service Unavailable” error when trying to access my CyberPanel dashboard. I believe I have traced the issue to a failing step during the installation/upgrade process, but I am now stuck and would appreciate some help.

Server OS Version:
Ubuntu 22.04 LTS

CyberPanel Version:
I cannot access the version management page due to the 503 error. I was attempting to install/upgrade to the latest stable version using the official upgrade script, which pulled v2.4.3 .

Problem Description & Steps Taken:

  1. My CyberPanel dashboard at https://<SERVER_IP>:8090 is showing a “503 Service Unavailable” error.

  2. I checked the status of the core services, and both are running:

  • systemctl status lscpd → active (running)

  • systemctl status lsws → active (running)

  1. Restarting the services with systemctl restart lscpd and systemctl restart lsws did not solve the issue.

  2. I ran the official upgrade/repair script: sh <(curl … preUpgrade.sh).

  3. The script fails consistently at the same point every time. Here is the error output from the script:

code Code

[2025-08-11 19:33:40] Installing WSGI-LSAPI...
tar: wsgi-lsapi-2.1.tgz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
/usr/local/cyberpanel_upgrade.sh: line 984: cd: wsgi-lsapi-2.1: No such file or directory
  1. To debug this, I tried to download the file manually. The first attempt revealed an SSL certificate issue:

code Code

root@localhost:~# wget https://open.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
--2025-08-11 19:36:53--  https://open.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
Resolving open.litespeedtech.com (open.litespeedtech.com)... 104.131.32.114
Connecting to open.litespeedtech.com (open.litespeedtech.com)|104.131.32.114|:443... connected.
ERROR: no certificate subject alternative name matches
        requested host name ‘open.litespeedtech.com’.
To connect to open.litespeedtech.com insecurely, use `--no-check-certificate'.
  1. Following the suggestion, I tried again with --no-check-certificate, but this revealed the true problem: a 404 Not Found error.

code Code

root@localhost:~# wget --no-check-certificate https://open.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
--2025-08-11 19:38:16--  https://open.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz
Resolving open.litespeedtech.com (open.litespeedtech.com)... 104.131.32.114
Connecting to open.litespeedtech.com (open.litespeedtech.com)|104.131.32.114|:443... connected.
WARNING: no certificate subject alternative name matches
        requested host name ‘open.litespeedtech.com’.
HTTP request sent, awaiting response... 404 Not Found
2025-08-11 19:38:16 ERROR 404: Not Found.

Log Files:
The CyberPanel main log (/home/cyberpanel/error-logs.txt) does not show any relevant errors, only routine SSL checks. The critical errors are all from the console output shown above.

It appears the wsgi-lsapi-2.1.tgz file is missing from the official LiteSpeed repository, which prevents the CyberPanel installation from completing, leading to the 503 error.

Could someone please confirm if this is a known issue or if the download URL in the script is outdated? Is there an alternative way to manually install this required WSGI-LSAPI component?

Thank you for your time and assistance.

3 replies
dd
ddegner #2

I am still having this problem. Am I the only one?

Bi
BigDaveAZ #3

nope. And you aren’t likely to get an answer from support either. I am looking to spin up a new VPS with a diffferent panel as there are no answers for this issue that is being shared here. Sorry, bro.

dd
ddegner #4

I stumbled across the answer. My DNS service was blocking www.litespeedtech.com

I have tail-scale installed on the server and it uses NextDNS which is more configured for my personal computers and blocks many things. Including litespeedtech.com

After allowing that the update completed.

Sign in to reply