Search results

You should use CloudFlare WAF to protect your site from unwanted access. Blocking unwanted requests by your host is not for free and causes extra load.

Yes, this could solve it.

What is the affected domaín about? Is it a parked domain in server control panel? If yes, is there any redirection (in server control panel) defined for this domain? Is the affected domain setuped in server control panel? Are there any custom nameservers defined for this domain?

Which CMS do you use?

This forum is for LiteSpeed Enterprise (LSWS). For OLS please use OLS support forum. https://forum.openlitespeed.org/

https://wordpress.org/search/utf8mb4_unicode_520_ci+intext%3A%22Plugin%3A+LiteSpeed+Cache%22/

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

Answer:

LSWS and OLS are just web servers, so why do ask for support for an issue that is not related to a web server? If you don't use a server control panel like cPanel or Plesk you need to study the related knowledge about how to administrate a Linux server.

@Mecanik This forum is for LiteSpeed Enterprise (LSWS). For OLS please use OLS support forum.

That's why a write (sub), so ignore it and use proxie for the domain(s).....

Create a "A" record for each (sub)domain to proxie a domain. This is the best method to benefit of CF and CF security without cache.

Support of LScache of WP plugin for WP has bin disontinued for years in this forum, so please WP support at LiteSpeed support at WordPress support forum: https://wordpress.org/support/plugin/litespeed-cache/

As already said, don't use CF cache, so disable CF caching. Use CF for proxy use ony, but never ever use CF cache and LiteSpeed cache at the same time!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Don't follow any CF settings regarding of CF cache lifetimes! DISABLE CF caching in any case! CF doesn't sync the cache with the content of the origin server!

You can use CF, but don't use CF cache as this will cause cache conflicts, so use CF proxy only. If you follow this advice everything behaves like it should.

You can use the OC plugin, but LiteSpeed's OC cache plugin has a lot of bugs and isn' t fully Journal ready, but there are OC users in this forum that have fixed these bugs, so install the OC cache plugin and check for any malfunctions. This forum can help you to fix it..

Search is your friend...;) https://wordpress.org/search/getimagesize+intext%3A%22Plugin%3A+LiteSpeed+Cache%22/

You should disable lazy load feature of the cache plugin for WP. This function has not only been outdated for years, but is also unnecessary because WP has also supported the better native lazy load for years. The native lazy load function does not require Javascript, so the problem described...

Where is the difference?! If the code is bad it cannot be perfect!