It works for sure. I have 8 domains that work as a reverse proxy. Read carefully what needs to be done. You redirect a non-standard port to work on a standard domain, i.e. on the server it runs on port xxxx but you have access as domain.ltd.
yum install lsphp71-pecl-imagick
Wczytane wtyczki: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Loading mirror s…
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:
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…
Whether through https:// ip:8090 or https://domain.com:8090 is:
This guide is out of date and does not work on the current version 1.9.1:
If I have access to CyberPanel
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 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…
I use login via ip:
I also checked through the domain:
In both cases, when domains are supported by cloudflare and port 8090 is unblocked, there is error 522.
Domains that have their own dns …
I did not want to work after installing CyberPanel and installing it by Docker.
I changed to such settings and it started working:
[Unit] Description=Docker Application Container Engine Documentation=http://docs.docker.com Af…
If port 8090 is unblocked then no domain supported by cloudflare will work. They show error 522. CyberPanel works. Domains with dns other than cloudflare work OK. You can perform operations in it. If I block port 8090, all domains supported by cloud…
I read about ports what you provided in the links.
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 th…
You misunderstood. If I have unblocked port 8090 to login in: https://ip:8090, websites that are supported by cloudflare will stop working. They will show error 522.
For them to work, I need to block port 8090 but then I can't use the cyberpanel bec…
Yes, I know what ports Cloudflare supports and that's why I'm surprised why port 8090 causes error 522. When I block port 8090, the domain starts working ok.
Hostname is not associated with Cloudflare. Only ip is connected.
The webadmin functions do not work:
How to add to cyberpanel what is described here: