Search results

Follow this instruction and you can remove "Disabled by CyberPanel": https://community.cyberpanel.net/t/how-to-enable-rewrite-rules-disabled-by-cyberpanel/34983

Actually, I was thinking of doing that through simlinks. thanks!

Do you think this is a good idea?

In OpenLiteSpeed we can specify custom 404, 403, etc. "Error" pages. I have created such pages. But the question is, is it possible to specify the path to them outside the root directory of the website? For example, if my templates are stored in a folder other than the domain folder. For...

You wrote that “the problem was with permission, after update to 1.8.1, fullchain.pem file has not good permission.” So, what were the permissions fullchain.pem before and after that? If you didn't make any changes, then it's 100% that this problem will happen again after the next upgrade.

We analyzed the permissions, and they were set as standard - 644 for fullchain.pem. There is another point in this situation - we also updated CyberPanel to the latest version, and it may have had such authority to overwrite the contents of this file.

On November 4, we updated in the same way, got the same problem, and solved it in the same way (instead cyberpanel we used certbot). We also had CyberPanel installed. Could you tell me what permissions you set on fullchain.pem and what permissions you had before? This is important so that...

We were pointed to a similar situation in this forum thread: https://forum.openlitespeed.org/threads/certificate-issue-after-update-to-1-8-1.6037/ It's similar with 100% accuracy. The owner solved the problem the same way we did - by deleting folders and reissuing certificates. But I still think...

Litespeed's technical support team told us that this had nothing to do with the update OLS, namely the lsup script. We were advised to investigate the issue ourselves. We have also updated CyberPanel to the latest version, so it is possible that this could be the cause. So, we will analyze it.

We have already reissued the certificate and the problem has been fixed, but I will still write to support about it. It might be a bug.

The certificate was valid, until December 2024. It was used for the Virtual host mail.kr-labs.com.ua, but at the same time it was listed as the primary certificate for the SSL Listener. Both contained paths to a valid LetsEncrypt certificate /etc/letsencrypt/live/... They were not changed or...

After upgrade OLS to 1.8 branch by lsup.sh, i unexpectedly saw, that my active and valid Lets Encrypt сertificate for domain mail.kr-labs.com.ua was changed with Litespeed self-signed cert. The paths to VirtualHost and Listener SSL were saved, but for some reason the content of the LE...