Nencio
About
- Username
- Nencio
- Joined
- Visits
- 475
- Last Active
- Roles
- Member
Comments
-
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.
-
Here's how to do: https://forums.cyberpanel.net/discussion/526/proxy-preserve-host
-
You need to install: 1. yum install MariaDB-server MariaDB-client galera 2. systemctl enable mysql.service 3. systemctl start mysql.service 4. reboot 5. Update Cyberpanel It should be OK.
-
By this error you cannot make bacap in the terminal.
-
Can I also install on versions 5.6 and 7.0?
-
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…
-
Can you write how to solve it in Centos?
-
Can you please update the guide? There is currently a libMagickWand.so.5 library error.
-
About this picture in the new login panel. You can see it in the picture I added. This is littering of a good admin panel.
-
What is this ad for: https://i.imgur.com/unlnEMG.png In this type of software you should not add links advertising a bottom bracket. There is already a link in the panel after logging in.
-
(Quote) I had such an entry with the blocked port 8090. Can you change this 8090 port to another one, e.g. 1234 in CyberPanel?
-
(Quote) 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-…
-
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: https://blog.cyberpanel.net/2018/12/25/how-to-remove-port-8090-from-cyberpanel/ Port 8090 conflicts with CF. Either you use CF…
-
Yes. Without CF, domains work OK.
-
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/
-
If I have access to CyberPanel https://ip:8090 https://i.imgur.com/FF5Ly69.png I have this error on all domains that are cloudflare: https://i.imgur.com/lBLYUOS.png If I block login to the cyberpanel and I don't have access, the domains work Ok. If …
-
(Quote) 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…
-
(Quote) 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.
-
(Quote) 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.
-
(Quote) For domains to work via cloudflare, port 8090 must be blocked. If the port is unblocked then domains served by cloudflare do not work because I have a 522 error.
-
I use login via ip: 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 …
-
It depends on the system. I have CyberPanel installed on Centos and a docker installed in CyberPanel. It works with and without the -n option.
-
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…
-
Please change the entry in: /etc/systemd/system/multi-user.target.wants/docker.service with: LimitNOFILE=1048576 on: LimitNOFILE=ulimit Restart: systemctl restart docker.service And check if it works.
-
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: 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
-
Hi I have added updated Polish translation on github.
