Search results

  1. M

    Litespeed for WP issues

    Sorry to disappoint you. That's the only way to make WP cache working properly. We do not see any simple solution that use either pure rewrite rule or Varnish VCL at server level can safely caching all different kind of WP installations. Something doom to fail, badly. As there are some many...
  2. M

    Litespeed for WP issues

    Are you using cPanel? or other control panel? For cPanel, cache plugin can be enabled server wide with a click of button, no need to go to individual site to install the cache plugin. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cpanel:whm-plugin-lscwp-management If not...
  3. M

    Litespeed for WP issues

    Have you use any other cache plugin successfully with you built-in CSS compression? Is it done at per page level, create a dedicate compressed css file for each page? If it is a plugin compatibility issue, need our developer to take a look.
  4. M

    Litespeed for WP issues

    Sorry about that, our wiki need to be updated, the outdated guide should be removed to avoid the confusion. The rewrite rule used defeated the WP cache plugin, have every page blindly cached. It is not the cache plugin's fault. Normally, you do not need to manually add any rewrite rule with...
  5. M

    Cached pages, Wordpress and the user toolbar

    You are following out-dated guide. The rewrite rule you tried is not from our cache plugin solution. We do not recommend using it now. Can you pointing me where you get that? We need to take it down. You do not have the plugin installed yet. It is much smarter as it hooks into WP internal logic.
  6. M

    Cached pages, Wordpress and the user toolbar

    You should use our Wordpress cache plugin now, those pure rewrite rule based WP caching is outdated. https://wordpress.org/plugins/litespeed-cache/
  7. M

    tls 1.1 and tls 1.2

    no problem.
  8. M

    [solved] First Byte Time optimization?

    Implement our cache solution. :-)
  9. M

    tls 1.1 and tls 1.2

    I thought you are talking about Litespeed Web Server, as this the support forum for our product. If you want curl to use TLS 1.1 on FreeBSD, you may need to upgrade OpenSSL and curl packages, or compile from ports.
  10. M

    tls 1.1 and tls 1.2

    You just change LSWS configuration to enable TLS 1.1 under the "SSL" tab of a listener or a vhost.
  11. M

    LSAPI Support for Perl

    We have one solution based on FastCGI. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:other-ext-apps:apache-mod-perl-equivalent
  12. M

    Setting up Litespeed on elastic beanstalk

    Thanks for those configurations, it looks indeed using mod_wsgi for python application. Our current support for mod_wsgi through Apache configuration is not enough, but it can be improved.
  13. M

    Setting up Litespeed on elastic beanstalk

    Can you show us the related Apache configuration? WSGIPath is a EB configuration, it should be converted to real Apache configuration, we need to know the real configuration used. You can PM me if you want. We may be able to make it work by simply reading Apache configuration.
  14. M

    Setting up Litespeed on elastic beanstalk

    Is it using Apache + mod_passenger to manage the python/django application? We do not have an installation script for EB yet. And it may require some manual configuration to make django application work.
  15. M

    Setting up Litespeed on elastic beanstalk

    What type of application you want to deploy through Elastic Beanstalk? Generally, you can replace Apache with LiteSpeed by configuring LiteSpeed to read Apache's configuration file.
  16. M

    [Solved] CageFS error when upgrading to LSWS 5.2.8

    I think it is harmless, we expect most people will use our wordpress cache plugin to speed up wordpress.
  17. M

    PHP CRIU support in CloudLinux environments.

    It could help a little bit.
  18. M

    QUIC shm data

    the SHM memory are reused, try to keep the size to minimum. it wont return to system though, the file size is the peak usage. Yes, you can remove them, then restart LSWS, it will start from fresh.
  19. M

    QUIC shm data

    check output ll /dev/shm/lsws/.quicshm*
  20. M

    oom killer on litespeed processes

    I think CloudLinux can give you better answer to this question, as they are the owner of this feature, producing this log message.
Top