Search results

FYI: I solved it. Not 100 percent perfect, but almost.

There is no good, better or bad configuration. LSWS comes as it is with the best configuration depending on your server configuration. FYI: All resources of your VPS are only virtual resources. That means 60GB Ram is VRAM only and can't be compared with RAM in a dedicated machine. The same with...

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

For everyone who is interested in how to get ESI work in non Wordpress application let's start an auction. You want to know what has to be done to get ESI work? The best price will solve it. I am open for requests.

You talk about version 5.4.1 of LiteSpeed webserver? Version 6.0.11 is already released since month. https://www.litespeedtech.com/products/litespeed-web-server/release-log

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

The reason is defined in status code 403 itself. Access forbidden because of (user) defined rules. https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.3 It seems there is a (rewrite) rule that blocks requests to sitemap.xml coming from specific user agents like "bot" or "sniffer".

Try this: For me on my test shared hosting server it works and is supported by LiteSpeed webserver. PHP scripts never stops and run for hours, but handle with care, if you don't have permissions to control running processes on your server. If so, you can't stop it!!!!! With this code script...

Yes, but there are not only cache plugins made by LiteSpeed. The world is greater than Wordpress and LSCWP. That's why I can't agree your philosophy about what should be cached or not. Of course, it has to be a goal. There are more arguments not to cache pages that have no status 200 than to...

Enable QUIC and you will get more than TCP Fast Open is able to fasten. QUIC is supported by all modern browsers and also Google itself uses QUIC.

Yes, I know, but Error 500 is only an example for all other != 200 status codes. What about 400, 401, 410, 30x?

To limit backup or to exclude files or directory from being backuped is part of control panel and not part of LiteSpeed. LSWS is only a webserver and not a software for server administration. So you should ask Plesk support.

Is there any known method to prevent error pages with status code 500 from being cached? Expressions to use them in .htaccess would do that, but are unsupported by LSWS. So what could help?

https://support.plesk.com/hc/en-us/articles/115000773605-How-to-exclude-specific-files-directories-from-a-backup-in-Plesk-

If you have cache plugin for Worpress check this: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

It seems there is no working synchronization between the current version and what WHM plugin detects what is current or not. You should leave it untouched to let WP users decide by their own if they automatically want to be notified if there is a new version available or not.

Sometimes, but only sometimes plugin support is a bit busy.

You did much, too much. Reset all settings and set do default. If done go to Wordpress cache plugin support and report your issue again or update the current thread. This forum is not the right place. Without physical access to your server nobody can help you. Maybe plugin support at Wordpress.

If you have OpenLiteSpeed instead of LiteSpeed webserver OLS should be restarted to make changes in .htaccess work

If you would have purged the cache in plugin settings and not browser cache the value for cache-control would not be 604800. Would please post your .htaccess file here?