Search results

When you have a valid cert with OLS, http/3 should be used by default. If you still have a configuration issue, feel free to join https://litespeedtech.com/slack and message me @eric from there, I can help to check the issue with you more quickly.

Maybe for LSWS, https://www.litespeedtech.com/support/forum/threads/litespeed-charset-problem.14549/ I saw you want to migrate site to OLS, since OLS does not support Apache modules and many custom rules in the .htaccess file, maybe you can try LSWS instead. ;)

Right, OLS does not support it.

"I first configured SSL on the normal site, but it didn't work, ", did you apply any certificate or upload any valid certificate? If there's no valid cert, then it will return the same result with a different HTTPS port listener. For 404 issue, did you put any domain value to the listener and...

I will forward the req to the team.

For OLS, you can set the header via Virtual Host > context > Header Operations, it may not check if it's empty or not. More example https://openlitespeed.org/kb/setting-up-cors-on-openlitespeed/

For OLS, you can set the header via Virtual Host > context > Header Operations More example https://openlitespeed.org/kb/setting-up-cors-on-openlitespeed/

It's not a bug, it is how you define the header. This is your current CSP from the header, content-security-policy: default-src https:; font-src https: data:; img-src https: data:; script-src https:; style-src https:; You might want to check...

No, but you can try the context feature with regular expression.

The cache seems working correctly. LSCache will be based on the URL, so, when you switch the URL, all cached files will be invalidated, that's why you saw the CPU spikes.

The context looks fine to me. I am not clear about how you set up the /httperror/404 page, it seems like you want to redirect to 404 by the App instead of the web server. If you want to custom OLS error page, please check https://openlitespeed.org/kb/custom-error-page/. About the 400 error, no...

May I know what is this CMS? If possible, please implement lscache to reduce the PHP process and MySQL load

Looks fine to me, do you have other listeners? If you have Slack, maybe you can join golitespeed community(https://litespeedtech.com/slack) and message me @eric from there, I will help you from there more quickly.

Inside of your /usr/local/lsws/conf/httpd_config.conf file, there's a section of listener, could you share the config here?

Dump the DB just in case. mysqldump -u root -p --all-databases > databasedump.sql Then you can edit the version e.g. 10.6 to 10.7 from "/etc/apt/sources.list.d/mariadb_repo.list" Then upgrade it with following commands apt update apt upgrade apt-get install mariadb-server systemctl...

For PM2 and Node connection timeout issue, it's not OLS related, maybe you could open a ticket here https://platform.cyberpersons.com/ or email to contact@cyberpanel.net

Could you submit the issue to bug@litespeedtech.com with the post link appended, we will check it further from there.

After you changed both the home and site URLs from blog.domain.com to domain.com/blog, please purge the cache and restart the web server and see if it helps to fix the issue. If not working, feel free to join LiteSpeed community on Slack and message me @eric from there.

Hi @meramsey Thanks for the information, I was replying to Vasdim's question about the lsphp72 package on Ubuntu 22.04. Correct, for Ubuntu 22, we will prepare lsphp74-81.

Thanks for the report @meramsey , it makes sense, will forward it to the team.