Search results

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.

For OLS as a reverse proxy, it won't take many resources, but I am not sure about the performance between Flask and fastapi+gunicorn, so no comment on it.

mmmm, then you might want to enable the rewrite log and check it from the error log, to see which rule has been matched.

Please try to copy the .htaccess file as a backup, then remove rules from "# BEGIN WP Rocket " to "# END WP Rocket ", restart lsws, and see if the webp starts loading.

No problem, glad to help. :)

If you manually run the certbot renew for this domain, what's the output in SSH console?

may I know if there's any control panel on this server? Did you get this error from control panel or OpenLiteSpeed web admin?

Try to replace RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteCond %{HTTPS} off RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] with RewriteCond %{HTTPS} off [OR] RewriteCond...

So the site URL you want to use is litti.biz, not www.litti.biz. But the following rules mean, if the URL does not start from www, then redirect to www. ``` RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] ```

@saiful iqmal Maybe you can send the issue to support@litespeedtech.com with this forum post link appended, we may help you directly from there and post the result here.