[Tutorial] How to setup and login to OpenLiteSpeed webadmin console

I'm sorry I'm bit of confused here, May I know what exactly is your issue here with CF?

Unlocked port 8090 on which you login in to CyberPanel causes error 522 on all domains that I have supported via cloudflare. These domains do not work.

when you mean unlocked port 8090 , what exactly does that mean ? and what was your URL to access it ? https://domain.com , or https://domain.com:8090?

when you mean unlocked port 8090 , what exactly does that mean ? and what was your URL to access it ? https://domain.com , or https://domain.com:8090?

If port 8090 is unlocked for logging into CyberPanel:
https://IP:8090
Domains that are supported by cloudflare do not work. They show error 522.

What was the link you were using to access it ? With domain

What was the link you were using to access it ? With domain

If CyberPanel is on port 8090 and it’s open, nothing on cloudflare dns is working and showing error 522.
If I block port 8090 with a firewall, everything starts working OK. All domains are starting to work.
I write the same yuk several times in this topic.
An open port 8090 prevents you from using cloudflare services.
There is a bug in the cyberpanel.

actually I am still not getting what is your issue here.

please join the discord and contact me @qtwrk there , I will ask for some details.

Best regards,

If I have access to CyberPanel
https://ip:8090


I have this error on all domains that are cloudflare:

If I block login to the cyberpanel and I don’t have access, the domains work Ok.
If I want domains to work, I can’t use the CyberPanel admin panel because port 8090 is blocked.

ok , so if you access https://ip:8090 , it works , right ?

and in this image https://i.imgur.com/lBLYUOS.png

what was your access ? https://domain.com , or https://domain.com:8090 ?

Whether through https:// ip:8090 or https://domain.com:8090 is:
https://i.imgur.com/lBLYUOS.png
This guide is out of date and does not work on the current version 1.9.1:
How to remove port 8090 from CyberPanel - #2 by lmilani - Blog Posts - CyberPanel Community

@Nencio said:
Whether through https:// ip:8090 or https://domain.com:8090 is:
https://i.imgur.com/lBLYUOS.png
This guide is out of date and does not work on the current version 1.9.1:
https://blog.cyberpanel.net/2018/12/25/how-to-remove-port-8090-from-cyberpanel/

And if you use domain without CF, it works?

Yes. Without CF, domains work OK.

Yes. Without CF, domains work OK.

when you say domains work , as https://domain.com it leads you to cyberpanel page, right ?

and actually I just did that tutorial on my test server and it works with CF enabled.

[root@cpanel ~]# curl -I -XGET https://xxxx.me
HTTP/1.1 200 OK
Date: Tue, 05 Nov 2019 22:29:06 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=d53b0fec021f1df12090596c39417413c1572992946; expires=Wed, 04-Nov-20 22:29:06 GMT; path=/; domain=.xxxx.me; HttpOnly; Secure
Cf-Railgun: direct (starting new WAN connection)
Content-Language: en
Set-Cookie: csrftoken=qDspwoxOsGBdGqW9aHOZxobghbmQKXciOHK4PadqwgTDH1Mr6B6Xx01RvhXCBtZp; expires=Tue, 03-Nov-2020 22:29:06 GMT; Max-Age=31449600; Path=/; secure
Vary: Cookie, Accept-Language,Accept-Encoding
X-Frame-Options: DENY
X-Turbo-Charged-By: LiteSpeed
X-Xss-Protection: 1; mode=block
CF-Cache-Status: DYNAMIC
Strict-Transport-Security: max-age=15552000
X-Content-Type-Options: nosniff
Expect-CT: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
Server: cloudflare
CF-RAY: 531243b99a6c97c0-FRA

as you can see , status 200 OK , and server: cloudflare

please check the screenshot , reverse proxy to panel with CF enabled , works.

you can see, CF extension indicates my connection is via their Amsterdam node with IP 104.27.149.241

so in your case, I think you may have some misconfiguration , in particular , I suspect something to do with options inside “SSL/TLS” tab

It does not lead to the cyberpanel page.
Leads to domain index.html.
This guide does not work on a new 1.9.1 installation:

Port 8090 conflicts with CF. Either you use CF with domains or CyberPanel admin login panel. At the same time, you can not use. CF has set up new hubs in Europe and may now be using CF 8090 proxy port for CF.
I have installed CyberPanel 2 times and each installation has the same error.

Guide:

Need to update.
How do I change the default CyberPanel login port from 8090 to another?
For me, the IP CF is different 104.27.174.39.

With the port 8090 operational:
curl -I -XGET https://xxxx.me
HTTP/2 522
date: Wed, 06 Nov 2019 02:40:21 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d279c7619aa7699fd58bb1ff1c256d2ef1573008015; expires=Thu, 05-Nov-20 02:40:15 GMT; path=/; domain=.xxxx.me; HttpOnly
cache-control: no-store, no-cache
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
set-cookie: cf_ob_info=522:5313b3a19a96d45b:HAM; path=/; expires=Wed, 06-Nov-19 02:40:51 GMT
set-cookie: cf_use_ob=443; path=/; expires=Wed, 06-Nov-19 02:40:51 GMT
expires: Thu, 01 Jan 1970 00:00:01 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
server: cloudflare
cf-ray: 5313b3a19a96d45b-HAM

With port 8090 blocked:
curl -I -XGET https://xxxx.me
HTTP/2 200
date: Wed, 06 Nov 2019 02:41:36 GMT
content-type: text/html
set-cookie: __cfduid=d047202eea0c9cd626ffe177fca90b27c1573008096; expires=Thu, 05-Nov-20 02:41:36 GMT; path=/; domain=.xxxx.me; HttpOnly
last-modified: Sat, 19 Oct 2019 06:18:22 GMT
vary: Accept-Encoding
x-turbo-charged-by: LiteSpeed
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
server: cloudflare
cf-ray: 5313b599188bd46b-HAM

what do you mean by “With port 8090 blocked:” ? how did you block it ?

what do you mean by "With port 8090 blocked:" ? how did you block it ?
You can block the port in the virtualization administration panel, e.g. proxmox. If you have a server at home, then in the router options.

There is an error in this guide:
https://blog.cyberpanel.net/2018/12/25/how-to-remove-port-8090-from-cyberpanel/
You need to replace:
extprocessor cyberpanel { type proxy address https://switch.cyberpanel.net:8090 maxConns 100 pcKeepAliveTimeout 60 initTimeout 60 retryTimeout 0 respBuffer 0 }

On:
extprocessor cyberpanel { type proxy address https://127.0.0.1:8090 maxConns 100 pcKeepAliveTimeout 60 initTimeout 60 retryTimeout 0 respBuffer 0 }

It will only work OK.

yes , if you use domain on backend addr , it will go through external network , where you use 127.0.0.1 , it doesn’t

yes , if you use domain on backend addr , it will go through external network , where you use 127.0.0.1 , it doesn't

I had such an entry with the blocked port 8090.
Can you change this 8090 port to another one, e.g. 1234 in CyberPanel?

yes , if you use domain on backend addr , it will go through external network , where you use 127.0.0.1 , it doesn't

I had such an entry with the blocked port 8090.
Can you change this 8090 port to another one, e.g. 1234 in CyberPanel?

I’m sorry to say not at this moment , 8090 was hard coded in LSCPD

please try block 8090 to outside world, but allow access by 127.0.0.1 and your server’s public IP

Please i need help, the open lite speed webadmin giving me error, was able to find the error log here.

/usr/local/lsws/conf/vhosts/*.zaddish.com/vhost.conf
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 1: docRoot: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 2: vhDomain: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 3: vhAliases: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 4: adminEmails: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 5: enableGzip: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 6: enableIpGeo: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 8: index: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 9: useServer: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 10: indexFiles: command not found
/usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 11: syntax error near unexpected token }' /usr/local/lsws/conf/vhosts/wildcard.zaddish.com/vhost.conf: line 11: }’

Help here please? i changed the domain name to a wildcard after creating a sub domain

thanks God bless you !