How To

Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt

You can install CyberPanel on a fresh Ubuntu server with one command. Twelve to fifteen minutes later you have OpenLiteSpeed, MariaDB, PowerDNS, Postfix, Pure-FTPd and a web panel on port 8090, but nothing makes that panel safe to use. It answers on the server IP with a self-signed certificate, opens 8090 to the whole internet, and its Deploy WordPress button leads to a paid page.

Original content from computingforgeeks.com - post 149507

This guide installs CyberPanel on Ubuntu 26.04 and 24.04 and then covers what someone with only a server and a domain needs next. That means Let’s Encrypt certificates for a website and the panel hostname, a new admin password, a firewall rule that limits the panel to your IP, and WordPress through WP-CLI instead of the paid WordPress Manager. Every command, prompt and error below was run on two fresh cloud VMs with CyberPanel 3.0.8 on Ubuntu 26.04 and 24.04 in November 2026. If you’d rather have the panel set up and looked after for you, our Squish Managed Cloud review tests a managed CyberPanel server.

What you need

CyberPanel wants the whole machine, because it installs its own web server, database, DNS and mail stack and takes over the firewall. Start from a clean server, not one already running Nginx or Apache:

  • Ubuntu 26.04 LTS or 24.04 LTS, fresh install, x86_64
  • At least 10 GB free disk (the minimum the installer shows on its menu)
  • A public IPv4 address, with root access over SSH
  • Two DNS names: one for the panel (panel.example.com) and one for your first site (example.com)
  • Inbound TCP 22, 80, 443 and 8090 allowed in your provider’s firewall, plus 8888 from your own IP if you want the browser terminal

Our test VMs had 2 vCPU and 4 GB RAM. Right after the install the panel reported 857 MB of RAM used on Ubuntu 26.04 and 944 MB on 24.04, with 8 GB of disk taken. Treat that as a floor for following along. What grows the number is the work you put on it: every busy WordPress site adds PHP workers, MariaDB wants its buffer pool to hold your databases, and the mail stack (Postfix, Dovecot, spam filtering) needs room of its own. A handful of small sites fits in 2 to 4 GB, while a server you plan to sell hosting on belongs on 8 GB or more.

Port 80 matters more than it looks. CyberPanel issues certificates with the HTTP-01 challenge, so Let’s Encrypt has to reach the server on port 80 for every name you secure. This works with any DNS provider, as long as the A records point straight at the server and not through a proxy.

Point DNS at the server and set the hostname

Create two A records at your DNS provider before you touch the server: panel.example.com and example.com, both pointing at the server’s public IP. Add a www record too if you want www.example.com in the certificate. When it’s missing, CyberPanel logs “www.example.com has no DNS records, excluding from SSL request” and issues the certificate for the bare name only.

Bring the system up to date first, because the installer pulls hundreds of packages and a half-upgraded box is where odd dependency failures come from:

sudo apt update
sudo apt -y upgrade
[ -f /var/run/reboot-required ] && sudo reboot

Both of our VMs needed that reboot after the upgrade. Once you’re back in, switch to a real root shell. It has to be sudo su -, because the installer checks the environment for a sudo session and refuses to run under sudo -i:

sudo su -

Set the two names once as shell variables so the rest of the commands run as written. Replace both values with your own, and run the export again if you open a new root shell later:

export PANEL_HOST="panel.example.com"
export SITE_DOMAIN="example.com"

Set the hostname to the panel name, then confirm both records resolve to the IP the server uses to reach the internet:

hostnamectl set-hostname "${PANEL_HOST}"
dig +short "${PANEL_HOST}" A
dig +short "${SITE_DOMAIN}" A
curl -4 -s https://ifconfig.me; echo

All three lines should print the same address. Standard Ubuntu cloud images ship dig; on a minimal image, add it with apt -y install bind9-dnsutils. If a dig line comes back empty, the record hasn’t propagated yet, and certificate issuance for that name will fail later, so wait until it resolves:

203.0.113.10
203.0.113.10
203.0.113.10

A different address on the last line usually means the server sits behind NAT, and then port 80 has to be forwarded to it before Let’s Encrypt can reach the challenge files.

Install CyberPanel on Ubuntu 26.04 or 24.04

The install command is the one-liner from the CyberPanel GitHub README. It downloads install.sh, which detects the OS and fetches the real installer. Run it from the root shell, and keep that SSH session connected until the installer finishes (the troubleshooting section explains what happened on Ubuntu 26.04 when we didn’t):

sh <(curl https://cyberpanel.net/install.sh || wget -O - https://cyberpanel.net/install.sh)

The installer asks eight questions. We took the default on everything except the first two menus, and this is the order they come in:

  1. Install CyberPanel / Exit: type 1
  2. OpenLiteSpeed or LiteSpeed Enterprise: type 1 for OpenLiteSpeed (Enterprise needs a paid license key)
  3. Full installation [Y/n]: Enter, which adds PowerDNS, Postfix and Pure-FTPd
  4. Remote MySQL [y/N]: Enter, for a local MariaDB
  5. Version: Enter for the latest release
  6. Memcached [Y/n]: Enter
  7. Redis [Y/n]: Enter
  8. WatchDog: Enter, which keeps the web and database services restarted if they die

There is no admin password prompt anymore. The script still prints “Choose [d]fault, [r]andom or [s]et password”, but the answer is hardcoded to random, so the password only appears in the summary at the end. Copy it when it shows up. If you miss it, the installer also keeps it in plain text in the root-only file /etc/cyberpanel/adminPass, so cat /etc/cyberpanel/adminPass recovers it. The summary below is from the Ubuntu 26.04 run, with the IP and password masked:

###################################################################
                CyberPanel Successfully Installed
                Current Disk usage : 8/28GB (31%)
                Current RAM  usage : 857/3907MB (21.93%)
                Installation time  : 0 hrs 12 min 0 sec
                Visit: https://203.0.113.10:8090
                Panel username: admin
                Panel password: ****************
             Run cyberpanel help to get FAQ info
             Run cyberpanel upgrade to upgrade it to latest version.
             Run cyberpanel utility to access some handy tools .
              Website : https://www.cyberpanel.net
              Forums  : https://forums.cyberpanel.net
              Wikipage: https://cyberpanel.net/KnowledgeBase/
              Docs    : https://cyberpanel.net/docs/
            Enjoy your accelerated Internet by
                CyberPanel & OpenLiteSpeed
###################################################################
Google Cloud Platform detected...
This provider has a network-level firewall
Please make sure you have opened following port for both in/out:
TCP: 8090 for CyberPanel
TCP: 80, TCP: 443 and UDP: 443 for webserver
TCP: 21 and TCP: 40110-40210 for FTP
TCP: 25, TCP: 587, TCP: 465, TCP: 110, TCP: 143 and TCP: 993 for mail service
TCP: 53 and UDP: 53 for DNS service
Your provider seems blocked port 25 , E-mail sending may not work properly.
Would you like to restart your server now? [y/N]:

The same run on Ubuntu 24.04 reported 15 minutes. The port list is worth reading: it’s what your provider’s firewall needs open for each service, and the port 25 warning is common on cloud VMs, where outbound mail is blocked until you ask the provider to lift it. We answered N to the reboot, since every service was already running. Confirm the version that landed:

cat /usr/local/CyberCP/version.txt; echo
/usr/local/lsws/bin/lshttpd -v | head -1

Both servers came up on the same panel build and OpenLiteSpeed release.

{"version": "3.0", "build": 8}
LiteSpeed/2.5.7 Open (BUILD built: Sat Oct 31 13:56:59 UTC 2026) 

The installer also removes UFW (apt-get -y remove ufw shows up in the apt history) and manages firewalld instead. If you had UFW rules on the box before, they are gone, and every firewall change from here happens in the panel or with firewall-cmd.

What differs between Ubuntu 26.04 and 24.04

The panel and OpenLiteSpeed are identical on both, but the parts the installer pulls from Ubuntu are not. The biggest one is Python. Ubuntu 26.04 ships Python 3.14 while the panel runs on Django 4.2, so on 26.04 the installer adds the deadsnakes PPA and builds the panel’s virtual environment on Python 3.12. These are the differences we measured on the two VMs:

ItemUbuntu 26.04Ubuntu 24.04
Installer sourcecyberpanel.sh from the GitHub stable branchcyberpanel.sh from cyberpanel.sh
Install time (summary)12 min15 min
Panel Python3.12.16 from ppa:deadsnakes (system Python 3.14.4)3.12.3, the system Python
MariaDB11.8.610.11.19
PHP versions installed8.2, 8.3, 8.4, 8.58.1, 8.2, 8.3, 8.4, 8.5
Default PHP in Create WebsitePHP 8.2PHP 8.1
Memcached servicememcachedlsmcd
RAM used after install857 MB944 MB

Two rows change what you do. The Create Website form preselects the oldest PHP on the box, so on 24.04 a site you create without looking gets PHP 8.1, which is past upstream security support, and the 26.04 default of PHP 8.2 loses security support at the end of December 2026. The 26.04 panel also lives on a PPA build of Python 3.12. An apt upgrade that touches the deadsnakes packages touches the panel too, so check that before you change Python on Ubuntu 26.04 for your own projects. The CyberPanel README’s support list still stops at 24.04, but the installer itself detects 26.04 and treats it as supported. It also still accepts 22.04, which we did not test.

Log in and change the admin password

Until the panel has its own certificate, open https://203.0.113.10:8090 (your server IP) and click through the browser’s self-signed certificate warning. Log in as admin with the password from the install summary. You land on the dashboard, with quick actions across the top and the server’s CPU, memory and disk use below them (our capture was taken later, so it already counts the two websites created further down):

CyberPanel dashboard after the first login on Ubuntu 26.04 with quick actions and usage overview

Replace the generated password with one you keep in a password manager. The adminPass tool (/usr/bin/adminPass, root only) does it from the shell, which also makes it the recovery path if you ever lose the password:

adminPass 'Use-A-Long-Unique-Passphrase'

It prints one line, and the old password stops working immediately.

Admin password successfully changed!

Single quotes keep the shell from expanding characters like $ or ! in the passphrase. Know what the tool does with it, though: /usr/bin/adminPass is a three-line script that sets the password, restarts lscpd and writes the new passphrase in plain text to /etc/cyberpanel/adminPass (mode 600, root only). The script writes it with an unquoted echo, so leave spaces and the characters *, ? and [ out of the passphrase, or the saved copy will not match. Anyone with root on the box can read it, so do not reuse that passphrase anywhere else. You can change it in the panel under Users & Plans > Modify User as well, but the shell command is the one that still works when you are locked out of the UI.

Create a website with a Let’s Encrypt certificate

Creating a website is also how you get its certificate. When the domain already resolves to the server, CyberPanel requests a Let’s Encrypt certificate as part of the same job, so there is no separate SSL step for the site. Open Websites > Create Website, pick the Default package and the admin owner, then fill in the form:

CyberPanel Create Website form with the domain, PHP 8.4 selected and the Create Website button on Ubuntu 26.04
  1. 1Domain Name
  2. 2Select PHP Version
  3. 3Create Website
  1. Type your site name (example.com) in Domain Name, and a real address you read in Email.
  2. Change Select PHP Version from the preselected oldest version. We used PHP 8.4, which current WordPress and most PHP apps support.
  3. Click Create Website and leave the page open until the progress box reads “Website successfully created.”

The job took under a minute on both servers, certificate included. Use a real email address. We typed [email protected], and the log shows CyberPanel quietly swapping it for one of its own (“Replacing invalid email with [email protected]”), so the ACME account behind the certificate ended up on an address we don’t control. The site lists as SECURE under Websites > List Websites:

CyberPanel List Websites page showing the site Active on PHP 8.4 with a SECURE Let's Encrypt badge

Click Manage on the site and the SSL card tells you who issued the certificate and how long it has left:

CyberPanel website manager SSL certificate card showing Let's Encrypt, Secure and valid for 89 days

Do not stop at the badge. Check what port 443 actually serves for the name, because on one of our servers the panel said SECURE while the browser got a different domain’s certificate (see the troubleshooting section):

echo | openssl s_client -connect "${SITE_DOMAIN}:443" -servername "${SITE_DOMAIN}" 2>/dev/null | openssl x509 -noout -issuer -subject -dates

The subject must match your domain and the issuer must be Let’s Encrypt. These certificates ran 90 days, from 16 November 2026 to 14 February 2027. Let’s Encrypt is moving its default to 64-day certificates in February 2027, which the panel’s weekly renewal check still covers.

issuer=C=US, O=Let's Encrypt, CN=YR2
subject=CN=example.com
notBefore=Nov 16 16:57:13 2026 GMT
notAfter=Feb 14 16:57:12 2027 GMT

The certificate files land in /etc/letsencrypt/live/example.com/. CyberPanel issues them with its own ACME client over HTTP-01, not with certbot, so certbot certificates won’t list them and you should not add certbot on top.

Secure the panel with a hostname certificate

The panel gets its certificate from a website of the same name, so the first step is a second website for panel.example.com. Create it exactly like the first one (Websites > Create Website, Default package, admin owner, any PHP version), and it picks up its own Let’s Encrypt certificate along the way. Running the panel on its hostname also unlocks the browser terminal: while you browse the panel by IP, each website page warns that “The Web Terminal will not work when accessed via IP.” The terminal also connects to the server on port 8888, so it only works once your provider’s firewall lets that port through from your address.

Then open Security > Hostname SSL (the page lives at /manageSSL/sslForHostName). It carries a note that the feature is deprecated in favour of a setup wizard, but it is still the page that does the job in this release:

CyberPanel SSL for Hostname page with the panel hostname website selected and the Issue SSL button
  1. 1Select Website
  2. 2Issue SSL

Pick panel.example.com under Select Website and click Issue SSL. On our 26.04 server the page then showed “Connection Error, Could not connect to server. Please refresh this page.” That message is the panel restarting with its new certificate, not a failure: the certificate was issued, and the next page load worked. Open https://panel.example.com:8090 and the login page loads with no warning:

CyberPanel login page on port 8090 served with a Let's Encrypt hostname certificate

Check port 8090 from the shell as well, since the browser hides the details:

echo | openssl s_client -connect "${PANEL_HOST}:8090" -servername "${PANEL_HOST}" 2>/dev/null | openssl x509 -noout -issuer -subject -dates

The panel now presents the Let’s Encrypt certificate for its own name.

issuer=C=US, O=Let's Encrypt, CN=YR2
subject=CN=panel.example.com
notBefore=Nov 16 17:00:43 2026 GMT
notAfter=Feb 14 17:00:42 2027 GMT

Behind the scenes, /usr/local/lscp/conf/cert.pem and key.pem become symlinks to the files in /etc/letsencrypt/live/panel.example.com/. That matters for renewal, which comes up further down. On the shell side, cyberpanel hostNameSSL --domainName "${PANEL_HOST}" does the same thing as the page, and it worked on our 24.04 server.

Restrict port 8090 in the firewall

Right after the install, firewalld lets the whole internet reach the panel login, plus two ports you probably do not use. List the rules the installer created for ports 8090, 7080 and 8888:

firewall-cmd --list-rich-rules | grep -E '8090|7080|8888'

Every one of them accepts any source address.

rule family="ipv6" port port="8090" protocol="tcp" accept
rule family="ipv4" source address="0.0.0.0/0" port port="7080" protocol="tcp" accept
rule family="ipv4" source address="0.0.0.0/0" port port="8090" protocol="tcp" accept
rule family="ipv4" source address="0.0.0.0/0" port port="8888" protocol="tcp" accept
rule family="ipv6" port port="7080" protocol="tcp" accept
rule family="ipv6" port port="8888" protocol="tcp" accept

Port 7080 is the OpenLiteSpeed WebAdmin console, and CyberPanel ships it switched off (disableWebAdmin 1 in /usr/local/lsws/conf/httpd_config.conf, nothing listens on it), so its rules do nothing useful. Port 8888 is the browser terminal’s backend (fastapi_ssh_server.service). Neither port appears in the panel’s Firewall page, so firewall-cmd is the only way to change them. Remove the 7080 rules:

firewall-cmd --permanent --remove-rich-rule='rule family="ipv4" source address="0.0.0.0/0" port port="7080" protocol="tcp" accept'
firewall-cmd --permanent --remove-rich-rule='rule family="ipv6" port port="7080" protocol="tcp" accept'
firewall-cmd --reload

Each command answers success. Next, limit 8090 to the address you manage the server from. Find it from your own computer, not the server, with curl -4 ifconfig.me. If that address changes often (home broadband, travel), use a VPN or bastion with a fixed IP instead, or you will lock yourself out every time it moves.

In the panel, open Security > Firewall. Under Firewall Rules, give the rule a name such as panel-myip, choose TCP, and fill in the rest:

CyberPanel Firewall Management page adding a TCP rule that allows port 8090 from one IP address
  1. 1IP Address
  2. 2Port
  3. 3Add Rule
  1. Enter your address with a /32 suffix in IP Address, for example 198.51.100.20/32.
  2. Enter 8090 in Port.
  3. Click Add Rule, check the new row appears at the bottom of the table, then click the red delete button on rule #1, the panel rule for 0.0.0.0/0.

Add your rule before you delete the open one. Done the other way round, the panel session you are using drops in the middle of the change. Deleting rule #1 removed the IPv4 and IPv6 open rules together on our server, which leaves one line for 8090:

firewall-cmd --list-rich-rules | grep 8090

Only your address is left on 8090.

rule family="ipv4" source address="198.51.100.20/32" port port="8090" protocol="tcp" accept

From the allowed address the login page still returned 200. From another server curl failed at once with “Couldn’t connect to server”, because firewalld rejects the connection. phpMyAdmin and the panel’s webmail link are served from port 8090 as well, so anyone who uses them from another address loses access too. If you lock yourself out, SSH on port 22 is not affected, so log in and put the open rule back:

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="0.0.0.0/0" port port="8090" protocol="tcp" accept'
firewall-cmd --reload

Port 8888 is still open to everyone, and the browser terminal behind it only works for someone who can reach 8090 anyway. Limit it to the same address. Set MY_IP to the one you allowed for 8090 (leave out the --add-rich-rule line to close 8888 completely if you never use the terminal):

export MY_IP="198.51.100.20"
firewall-cmd --permanent --remove-rich-rule='rule family="ipv4" source address="0.0.0.0/0" port port="8888" protocol="tcp" accept'
firewall-cmd --permanent --remove-rich-rule='rule family="ipv6" port port="8888" protocol="tcp" accept'
firewall-cmd --permanent --add-rich-rule="rule family=\"ipv4\" source address=\"${MY_IP}/32\" port port=\"8888\" protocol=\"tcp\" accept"
firewall-cmd --reload
firewall-cmd --list-rich-rules | grep -E '8090|8888'

Each change answers success, and the last command should list exactly two rules, both limited to your address:

rule family="ipv4" source address="198.51.100.20/32" port port="8090" protocol="tcp" accept
rule family="ipv4" source address="198.51.100.20/32" port port="8888" protocol="tcp" accept

Your provider’s firewall sits in front of all this. On a cloud VM you can make the same restriction there (allow 8090 only from your IP), which is the safer place for it because a panel bug or a reinstall can’t undo it.

Install WordPress with WP-CLI

In this release, both the Deploy WordPress card on the dashboard and the WordPress menu send you to /websites/pricing, the sales page for the paid WordPress Manager. The cyberpanel installWordPress command is no way around it either: on our 24.04 server it exited without a word and installed nothing. WP-CLI does the whole job for free, and it keeps the files owned by the site’s own Linux user, which is how CyberPanel isolates sites from each other.

This section is optional and only needs the website you created earlier. Still in the root shell, set its values. CyberPanel names the site user from the first five letters of the domain plus four random digits (example.com gives something like examp1234), so read it from the folder instead of guessing:

export SITE_DOMAIN="example.com"
export WP_ROOT="/home/${SITE_DOMAIN}/public_html"
export SITE_USER=$(stat -c %U "${WP_ROOT}")
export DB_NAME="wpdb01"
export DB_USER="wpuser01"
export DB_PASS="Change-This-Db-Password-2026"
export ADMIN_EMAIL="[email protected]"
echo "Site user: ${SITE_USER}"

WP-CLI is not part of the CyberPanel install, so fetch the official phar and put it on the path. It runs on the PHP CLI the installer linked (PHP 8.3 from /usr/local/lsws/lsphp83 on both of our servers):

curl -sO https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
install -m 0755 wp-cli.phar /usr/local/bin/wp
wp --version --allow-root

It reports its version.

WP-CLI 2.12.0

Create the database through CyberPanel rather than straight in MariaDB, so it appears under the website in the panel and counts against its package. The command prints a screen of Python SyntaxWarning lines on stderr on both Ubuntu releases, which is why that stream goes to /dev/null:

cyberpanel createDatabase --databaseWebsite "${SITE_DOMAIN}" --dbName "${DB_NAME}" --dbUsername "${DB_USER}" --dbPassword "${DB_PASS}" 2>/dev/null

Read the errorMessage field, not success. A good run says None; on 24.04 our first attempt printed "success": 1 next to an access denied error and created nothing (covered below):

{"success": 1, "errorMessage": "None"}

Now move into the document root. This step is not cosmetic. WP-CLI looks for wp-cli.yml in the current directory, and some of its commands start a child process in that directory as the site user. From /root, which the site user can’t read, wp rewrite structure failed with a posix_spawn() failed: Permission denied error. The wp-cli.yml file tells WP-CLI that rewrite rules are available, since it cannot detect OpenLiteSpeed’s rewrite engine on its own and otherwise refuses to write .htaccess:

cd "${WP_ROOT}"
printf 'apache_modules:\n  - mod_rewrite\n' | sudo -u "${SITE_USER}" tee wp-cli.yml

Download WordPress, write wp-config.php and run the install, all as the site user:

sudo -u "${SITE_USER}" wp core download
sudo -u "${SITE_USER}" wp config create --dbname="${DB_NAME}" --dbuser="${DB_USER}" --dbpass="${DB_PASS}" --dbhost=localhost
sudo -u "${SITE_USER}" wp core install --url="https://${SITE_DOMAIN}" --title="Example Site" --admin_user="siteadmin" --admin_email="${ADMIN_EMAIL}"

Without --admin_password, WP-CLI generates one and prints it once, so save it before you scroll on:

Downloading WordPress 7.1.4 (en_US)...
md5 hash verified: e3ab64c0de73fe22c0e482c00fa9298c
Success: WordPress downloaded.
Success: Generated 'wp-config.php' file.
Admin password: ************
Success: WordPress installed successfully.

Switch to post-name permalinks and add the LiteSpeed Cache plugin, which is what OpenLiteSpeed’s page cache keys off. Delete CyberPanel’s “CyberPanel Installed” placeholder index.html as well. The vhost lists index.php first, so WordPress wins anyway, but the placeholder has no reason to stay public:

sudo -u "${SITE_USER}" wp rewrite structure '/%postname%/' --hard
sudo -u "${SITE_USER}" wp plugin install litespeed-cache --activate
rm -f index.html

Both commands end in Success lines, and the rewrite command flushes .htaccess on its own because of wp-cli.yml:

Success: Rewrite structure set.
Success: Rewrite rules flushed.
Installing LiteSpeed Cache (7.9.3)
Downloading installation package from https://downloads.wordpress.org/plugin/litespeed-cache.7.9.3.zip...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Activating 'litespeed-cache'...
Plugin 'litespeed-cache' activated.
Success: Installed 1 of 1 plugins.

Give it three minutes before you test the cache. Right after the install we saw 200 responses with no x-litespeed-cache header at all, because OpenLiteSpeed only reads the plugin’s new .htaccess rules when CyberPanel’s olsHtaccessReload.py cron reloads the site, every three minutes. Then request the sample page three times:

for i in 1 2 3; do curl -s -o /dev/null -D - "https://${SITE_DOMAIN}/sample-page/" | grep -i "x-litespeed-cache:\|^HTTP"; done

A miss and then hits means the permalink resolves and pages come out of OpenLiteSpeed’s cache.

HTTP/2 200
x-litespeed-cache: miss
HTTP/2 200
x-litespeed-cache: hit
HTTP/2 200
x-litespeed-cache: hit

No header at all means the reload has not happened yet, so wait and try again. Log in at https://example.com/wp-admin/ with siteadmin and the printed password, and the site is done.

Check certificate renewal

Renewal is already scheduled, but not by the tool you might expect. Two root cron jobs touch certificates:

crontab -l | grep -E 'renew|acme'

The acme.sh line’s minutes and hours are random per install (24.04 got 55 1,7,13,19), while the renew.py line is the same everywhere:

28 5,11,17,23 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null
45 4 * * 4 /usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/renew.py >/dev/null 2>&1

The acme.sh job doesn’t renew these certificates. CyberPanel issued them with its own ACME client, so acme.sh answers “is not an issued domain, skipping” for every one of them. The job that matters is renew.py, every Thursday at 04:45, which renews any certificate with fewer than 15 days left. You can manage certificates with acme.sh on a plain server, but on a CyberPanel box leave renewal to the panel. Run the job by hand to see what it decides:

/usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/renew.py 2>/dev/null

Fresh certificates are skipped, and the log gives you the days left for each.

[11.16.2026_18-12-13] Running SSL Renew Utility
[11.16.2026_18-12-13] Checking SSL for example.com.
[11.16.2026_18-12-13] SSL exists for example.com. Checking if SSL will expire in 15 days..
[11.16.2026_18-12-13] Provider: Let's Encrypt, Days until expiration: 89
[11.16.2026_18-12-13] SSL exists for example.com and is not ready to renew, skipping..
[11.16.2026_18-12-13] Checking SSL for panel.example.com.
[11.16.2026_18-12-13] SSL exists for panel.example.com. Checking if SSL will expire in 15 days..
[11.16.2026_18-12-13] Provider: Let's Encrypt, Days until expiration: 89
[11.16.2026_18-12-13] SSL exists for panel.example.com and is not ready to renew, skipping..

One gap is worth closing. When renew.py renews something, it restarts Postfix and reloads Dovecot but deliberately not lscpd, the panel process (a comment in the script says restarting it would kill running backup workers). The panel’s certificate files are symlinks, so they update on disk, but the running panel can keep serving the old certificate until it restarts. A weekly restart an hour after the renewal job covers it:

(crontab -l; echo '45 5 * * 4 /usr/bin/systemctl restart lscpd') | crontab -

We restarted lscpd by hand on the 26.04 server to confirm it comes straight back on the hostname certificate, which it did. Schedule the restart outside your backup window if you use CyberPanel’s backups.

Fix common CyberPanel install errors

Every error below happened on our two lab servers, with the exact text the installer, panel or tool printed.

“You are using SUDO , please run as root user…”

The installer exits right after “Checking root privileges” when it finds sudo variables in the environment, which is what sudo -i and sudo bash leave behind. Run sudo su - (with the dash) and start the one-liner again from that shell.

Installer stops at “Starting main installation” on Ubuntu 26.04

Our first 26.04 run died a few minutes in, with the last progress line reading “Starting main installation..,30”. We had started it inside tmux and then closed the SSH connection that launched tmux. Seconds after the installer’s system tweak step restarted systemd-networkd and systemd-resolved, systemd-logind restarted as well, logged “Leader of session ‘4’ is gone while deserializing”, and stopped that session, taking tmux and the installer down with it. CyberPanel’s own installer code notes that newer systemd releases end the installer’s SSH session when logind restarts, and it skips that restart on 26.04, but ours went down at an earlier one. Start from a fresh VM (a half-finished install leaves services and swap behind), run the installer from an SSH session, and keep that connection open until the summary prints. Our rerun that way finished cleanly.

“Connection Error Could not connect to server. Please refresh this page.”

This appeared after clicking Issue SSL on the Hostname SSL page. The panel restarts to load the certificate and the open page loses its connection. Wait a few seconds, then load https://panel.example.com:8090 and check port 8090 with the openssl s_client command from the hostname section.

“SSL: no alternative certificate subject name matches target hostname”

On 24.04 we created the panel website and the site website from the shell with cyberpanel createWebsite, then ran cyberpanel hostNameSSL. Both certificates were issued, yet curl to the site failed with this error and port 443 served the panel’s certificate for the site name. The site’s vhost.conf had no vhssl block, and its name was mapped only on the IPv6 SSL listener. Re-issuing the site certificate rewrote the vhost and fixed it:

cyberpanel issueSSL --domainName "${SITE_DOMAIN}" 2>/dev/null

The same Issue SSL button sits on each site in Websites > List Websites. Afterwards openssl s_client showed the right subject and curl returned 200. The sites we created through the panel on 26.04 never hit this, which is one more reason to run the openssl check rather than trust the SECURE badge.

“(1045, Access denied for user ‘wpuser01’@’localhost’ (using password: YES))”

Our first cyberpanel createDatabase on 24.04 returned "success": 1 with this text in errorMessage, and created neither the database nor the user, so the next step failed with “Error: Database connection error (1045) Access denied”. Running the identical command again worked. Check that both objects exist before you write wp-config.php:

mariadb -e "SHOW DATABASES LIKE '${DB_NAME}'; SELECT User,Host FROM mysql.user WHERE User='${DB_USER}';"

A healthy result lists the database and the user twice, once for localhost and once for 127.0.0.1. An empty result means rerun createDatabase.

“proc_open(): posix_spawn() failed: Permission denied”

Running sudo -u "${SITE_USER}" wp ... rewrite structure '/%postname%/' --hard from /root printed this warning, then a PHP fatal error: “proc_close(): Argument #1 ($process) must be of type resource, false given”. WP-CLI spawns a second process to flush the rules, and that process can’t start in a directory the site user is not allowed to read. From a readable directory without wp-cli.yml, the same command instead warns “Regenerating a .htaccess file requires special configuration” and writes no rewrite rules, so permalinks return 404. Both go away when you cd "${WP_ROOT}" and create wp-cli.yml as shown in the WordPress section.

If CyberPanel’s one-command install and its paid WordPress tier do not suit you, HestiaCP on Ubuntu gives you an Nginx and Apache stack with no paid tier, and our comparison of free hosting control panels covers the rest. For a single site that doesn’t need a panel at all, a standalone OpenLiteSpeed install gives you the same web server with far fewer moving parts.

Keep reading

Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) Ubuntu Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Security UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Backup and Restore Linux Systems with Timeshift Debian Backup and Restore Linux Systems with Timeshift Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Cloud Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Squish Managed Cloud Review: CyberPanel Hosting, Tested Cloud Squish Managed Cloud Review: CyberPanel Hosting, Tested How To Install MySQL 8.0 on Debian 12/11/10 Databases How To Install MySQL 8.0 on Debian 12/11/10

2 thoughts on “Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt”

  1. I work with CyberPanel. One detail to add after the hostname step: editing /etc/hosts affects the server itself; the domain also needs public DNS pointing at the server before website deployment and certificate validation. For readers continuing from your final Websites screenshot, the current WordPress workflow creates the site and database together and checks the domain first. Our updated walkthrough includes the package, owner, and administrator fields.

    Reply
    • Correct, /etc/hosts only fixes local resolution. The A record has to point at the server before Let’s Encrypt validation will pass, which is why the SSL step comes after DNS here.

      Reply

Leave a Comment

Press ESC to close