Knowledge Base

Details

Parent Category: Servers

Category: CyberPanel

https://YOUR_IP:8090/snappymail/?admin

cat /usr/local/lscp/cyberpanel/rainloop/data/_data_/_default_/admin_password.txt

mysql:host=localhost;dbname=cyberpanel;charset=utf8

cat /etc/cyberpanel/mysqlPassword

UPDATE e_users SET password = :newpass WHERE email = :email AND emailOwner_id = :domain

Details

Parent Category: Servers

Category: CyberPanel

/usr/local/lsws/admin/misc/admpass.sh

Make sure to open port 7080 in firewall.

goto host.websitedomain.com:8090/firewall/

Details

Parent Category: Servers

Category: CyberPanel

• SSL

Debugging certificate requesting issues when a self-signed certificate is created instead.

Run from SSH:

/root/.acme.sh/acme.sh --issue -d <YOUR_DOMAIN> -d www.<YOUR_DOMAIN> --cert-file /etc/letsencrypt/live/<YOUR_DOMAIN>/cert.pem --key-file /etc/letsencrypt/live/<YOUR_DOMAIN>/privkey.pem --fullchain-file /etc/letsencrypt/live/<YOUR_DOMAIN>/fullchain.pem -w /home/<YOUR_DOMAIN>/public_html --force --debug

You might find these lines of warning showing in a slightly different color [depending on your ssh terminal]:

[Friday 07:07:2021 00:00:11 PM UTC] No EAB credentials found for ZeroSSL, let's get one
[Friday 07:07:2021 00:00:11 PM UTC] acme.sh is using ZeroSSL as default CA now.
[Friday 07:07:2021 00:00:11 PM UTC] Please update your account with an email address first.
[Friday 07:07:2021 00:00:11 PM UTC] acme.sh --register-account -m [email protected]
[Friday 07:07:2021 00:00:11 PM UTC] See: https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-C

New CyberPanel 2.1+ has switched suddenly to use of zerossl as the default certificate authority instead of LetsEncrypt certificate authority.
This will likely limit your ssl certificate freedom as it is likely just acting as a third party between you and LetsEncrypt.org, to put a cap on and charge you when you reach a certain number of certificates for your cyberpanel deployment.

If you're ok with zerossl acting as default and go-between run the command the debugger recommended, substituting [email protected] with your actual email address:

/root/.acme.sh/acme.sh --register-account -m [email protected]

 Or change the default back to the legitimately preferred certificate authoritive LetsEncrypt, running this command:

/root/.acme.sh/acme.sh --set-default-ca --server letsencrypt
[Friday 07:07:2021 00:00:11 PM UTC] Changed default CA to: https://acme-v02.api.letsencrypt.org/directory

Details

Parent Category: Servers

Category: Litespeed Webserver

Before proceeding with the changes, first of all, we've to check the current CLI PHP version, so run:

php -v

The output may be like this:

[root@elnath]# php -v
PHP 7.1.33 (cli) (built: Nov 22 2019 11:40:51) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.1.33, Copyright (c) 1999-2018, by Zend Technologies
[root@elnath]#

As we can see, PHP version 7.1 is set as the CLI PHP. If you have certain needs and PHP 7.1 does not work for certain applications you can run the following command to update the default PHP on CLI:

ln -s /usr/bin/php /usr/local/lsws/lsphp81/bin/php

ln -s /usr/bin/php /usr/local/lsws/lsphp80/bin/php

ln -s /usr/bin/php /usr/local/lsws/lsphp74/bin/php

ln -s /usr/bin/php /usr/local/lsws/lsphp73/bin/php

ln -s /usr/bin/php /usr/local/lsws/lsphp72/bin/php

Please run any of those command lines as per your needs.

How to use specific PHP Version in your Cron Jobs?

Some applications require you to set cron jobs and they require PHP CLI executable. Now rather than changing the default global PHP binary version, you can use a direct path to that CLI.

For example, if an application requires that its script should be running through PHP 8.1, you can use the direct path for its binary rather than updating a global binary, such as:

/usr/local/lsws/lsphp81/bin/php <your command goes here>