Recent content by LiteCache

  1. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    @neikoloves I've created a special FAQ for you so you can get an idea of what LiteCache Rush is and what it's good for. If you have any further questions, please be patient for a few more days until Rush is available. What is Rush? Rush is a plugin-loading controller for WordPress. It does not...
  2. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    Open your mind. ;) The internet provides other indicators to distinguish between good and bad guys. Using IP addresses for filtering is not only insecure, but actually outdated.
  3. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    LiteCache is a registered trademark, and most LiteCache solutions are either based on or designed exclusively for LiteSpeed. LiteCache for Enterprise CMS is a replacement for LiteSpeed LiteMage.
  4. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    It's not a question of trust. You're trying to protect yourself, and that's fine, but the method you're using to protect yourself is wrong. If you want to stick with this method, then by all means, continue to feel safe. But be aware that server security isn't based on outdated client-side...
  5. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    I wish you the best of luck in your search for alternatives. However, you probably won't have any luck, because the WordPress community still hasn't grasped the root cause of the problem. So don't waste any more time, disable ESET and learn how to truly solve WordPress performance issues.
  6. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    While concealing your identity through various means might enhance your safety, it also increases the risk of being identified as a "bad guy" and consequently blocked incorrectly. Traditional methods may work to disguise your identity, but they rely on flawed and outdated criteria. ESET is good...
  7. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    The country doesn't matter in your case, so again, request cachecrawler.com host and tell me your IP address.
  8. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    The last block with rayID 9a8b0552c8be97ed was detected by an user that has Chrome version 109. This version in combination with other conditions leads to the block. However, request cachecrawler.com again and tell me the IP address.
  9. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    The reason you are being blocked: You are using a Chrome browser version that has been considered outdated since 2023.
  10. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    I'm sorry again if you're still blocked. We don't use CF filter rules, but rather custom rules that have proven effective for 20 years. To determine the reason for your block, please send me your IP address via private message.
  11. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    Sorry for the block. Unfortunately, you're using an access provider that many "bad guys" use, but you should now have unrestricted access. LiteCache Rush is finished, but it's currently undergoing practical testing with selected users, so you'll likely have to wait until the end of December...
  12. LiteCache

    LiteCache Rush: WordPress Performance by Prevention

    Would you please tell me which country you are from?
  13. LiteCache

    set_time_limit(3600 * 48); but process ever run only by three hours, how fix that?

    @neikoloves Before we talk about your post, we need to clarify what you are referring to, because the topic of this thread is something completely different.
  14. LiteCache

    exists a file to config "LSAPI_MAX_PROCESS_TIME" for all server? where it is?

    LSAPI_MAX_PROCESS_TIME This variable must be set and changed in web server configuration and cannot be defined in .htaccess. Just read the documentation (for LSWS) as already posted in...
  15. LiteCache

    set_time_limit(3600 * 48); but process ever run only by three hours, how fix that?

    LiteSpeed Enterprise (LSWS) uses LSAPI_MAX_PROCESS_TIME Environment Variable https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#set-lsapi_max_process_time-environment-variable But don't know if OLS supports it. If not, run the script in console.
Top