in Cyberpanel, some advanced configuration needs to be done in OLS webadmin console.
how to:
first , run this line in SSH to setup login info for webadmin console
/usr/local/lsws/admin/misc/admpass.sh
and then, login into CyberPanel , and add TCP 7080 port to firewalld in order to access it.
and please don't forget to reload the firewalld once new rule is added.
after that , you can know access it by https://Server-IP:7080
and with the login info you set in SSH.
the console itself currently comes with Chinese, English and Japanese.
of course , anyone who wishes to translate to his/her language is more than welcome
original posted here by myself , and translated by myself
Comments
OLS web adm panel looks pretty concise, and this advantage can be integrated into CyberPanel. Why the panel leaves this untouched and hasn't had it connected? I previously thought the web server section/module inside the panel is 'outsourced' to OLS web admin panel.
OLS supports different distros while Cyber cannot. What a pity.
there is docker image now , you can try on other distros.
I'm using a hostname for cyberpanel with valid cert.
either replace these 2 with your current cert , or change its path in webadmin console.
Replacing or moving it will fail auto renew I think.
Please include this on future update.
I can´t make the SSL work in :7080 ;(
in the webadmin settings i have:
PRIVATE KEY : /etc/letsencrypt/live/MYDOMAIN.com/privkey.pem
CERTIFICATE FILE: /etc/letsencrypt/live/MYDOMAIN.com/fullchain.pem
both are the correct SSL for the domain.
But when i go to https://MYDOMAIN.com:7080 i get "invalid SSL"
always appears the certificate of webadmin..
Thanks for any help.
Fabian
was in another section.. i put the paths:
PRIVATE KEY : /etc/letsencrypt/live/MYDOMAIN.com/privkey.pem
CERTIFICATE FILE: /etc/letsencrypt/live/MYDOMAIN.com/fullchain.pem
and now.. i can´t logn anymore in the webadmin ;(
F.
cyberpanel is ON and i can login to :8090
BUt litespeed is DOwn
I can´t restart it in any way
"Could not fetch details, either LiteSpeed is not running or some error occurred, please see CyberPanel Main log file."
when i press in "LIcence Status" i got:
Operation Failed!
Command '['sudo', 'cat', '/usr/local/lsws/conf/serial.no']' returned non-zero exit status 1
All was working perfect! ;( not nothing works..
I would appreciate any help
Thanks
Fabian
was a very stupid mistake..
i write here as example: "/etc/letsencrypt/live/MYDOMAIN.com/privkey.pem"
and i put exactly that in the webadmin.. and "MYDOMAIN.com" was the problem
i fixed it from ssh, restarted LS and all is working like a charme now.. including the webadmin at :7080 with SSL
Regards and sorry for the previous posts
Thanks
Fabian
But in the browser it remains "Connecting..." Any idea?
It never connects me. Something like how much the web server is stopped that does not release error but stays connected. But in this case the web server is working normally.
[SOLVED]
Solution: Open port 7080 in CyberPanel Firewall
The error log reads as follows:
2019-09-04 17:21:21.690291 [INFO] [Module: modcompress 1.1] has been initialized successfully
2019-09-04 17:21:21.690397 [INFO] [Module: moddecompress 1.1] has been initialized successfully
2019-09-04 17:21:21.690470 [INFO] [Module: cache 1.61] has been initialized successfully
2019-09-04 17:21:21.690535 [INFO] [Module: mod_security Mod_Security 1.1] has been initialized successfully
2019-09-04 17:21:21.690590 [ERROR] [SSL] Config SSL Context with Certificate File: /usr/local/lsws/usr/local/lsws/admin/conf/webadmin.crt and Key File:/usr/local/lsws/usr/local/lsws/admin/conf/webadmin.key get SSL error:
2019-09-04 17:21:21.690597 [ERROR] [config:admin:listener:adminListener:ssl] failed to create new SSLContext for *:7080
2019-09-04 17:21:21.690602 [ERROR] [config:admin:listener] No listener is available for admin virtual host!
2019-09-04 17:21:21.690614 [ERROR] Fatal error in configuration, exit!
The error seems to be in the line where it's looking for the cert and key file in /usr/local/lsws/usr/local/lsws/admin/conf
I can SSH into the server. Any suggestions on where to find the config file to edit, and what the correct values should be?
https://github.com/usmannasir/cyberpanel/commit/9bedc44487333bc06a29cea62991471ed98f011a
If you want to do this manually until then without having to do it via the webadmin settings it can easily be done via the below commands.
LSWebadmin
mv /usr/local/lsws/admin/conf/cert/admin.crt /usr/local/lsws/admin/conf/cert/admin.crt-bak
mv /usr/local/lsws/admin/conf/cert/admin.key /usr/local/lsws/admin/conf/cert/admin.key-bk
ln -s /usr/local/lscp/conf/cert.pem /usr/local/lsws/admin/conf/cert/admin.crt
ln -s /usr/local/lscp/conf/key.pem /usr/local/lsws/admin/conf/cert/admin.key
OLS webadmin
mv /usr/local/lsws/admin/conf/webadmin.crt /usr/local/lsws/admin/conf/webadmin.crt-bak
mv /usr/local/lsws/admin/conf/webadmin.key /usr/local/lsws/admin/conf/webadmin.key-bk
ln -s /usr/local/lscp/conf/cert.pem /usr/local/lsws/admin/conf/webadmin.crt
ln -s /usr/local/lscp/conf/key.pem /usr/local/lsws/admin/conf/webadmin.key
restart lsws/ols
service lsws restart
https://i.imgur.com/zVQihv3.png
How to add to cyberpanel what is described here:
https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:cloudflare-ips-or-subnets
For them to work, I need to block port 8090 but then I can't use the cyberpanel because without the port unblocked I won't be able to access it.
CF only allows certain ports to be reverse-proxyed
And I don't know why port 8090 causes conflict and error 522.
That's why I wrote this topic. I have default ports in the firewall after a new installation + 7080.
I did the installation twice and the problem repeated.
For some reason, a new CyberPanel installation causes such a conflict.
you mean like you were accessing something like `https://panel.domain.com:8090` and you got 522 ?
what if you access it directly https://YOUR_SERVER_IP:8090 ?
https://YOUR_SERVER_IP:8090
I also checked through the domain:
https://panel.domain.com:8090
In both cases, when domains are supported by cloudflare and port 8090 is unblocked, there is error 522.
Domains that have their own dns work OK.
If the port is unblocked then domains served by cloudflare do not work because I have a 522 error.
https://IP:8090
Domains that are supported by cloudflare do not work. They show error 522.