Search results

If you run redis-cli from the SSH console, does the connection work?

Hi, It was introduced with v1.7.19 and has been fixed with v1.7.19 build 2. If you installed it from the LiteSpeed repo, then you can run the package update to have the new version installed.

You can simply update system packages on the origin server, e.g. "apt update && apt upgrade -y". Otherwise, you can launch a new server, and migrate the data from the old server to the new one. Let me know if you have any questions.

For subdomains, you can set up a wildcard certificate. For different domains, you might want to set up multiple virtual hosts, so you can apply different SSL certificates. If you have a test server, can test the virtual host script, which generates virtual hosts much more quickly and easily...

@eXRuLeZz If QC cannot reach the origin server, you should get a 520 status code, may I know if this is the case?

Please submit the issue to support@litespeedtech.com with this forum post link appended for further support.

ok, if you find any method to reproduce it, please post it again.

Good to know it works now.

@sbmg18 I saw your ticket has been resolved, was it due to the cache module setup?

No problem.

Was it under some kind of attack or PHP loop, or simply it's a high-traffic site? For high-traffic site, maybe you can implement LSCache to reduce the PHP load and process number.

I am not sure about DA, but cPanel does not support OS upgrades, they recommend you to set up a new server, and then transfer the data. You might want to search DA docs if they support it or not. Your PHP packages are built on Ubuntu 20.04, it might not work with Ubuntu 22.04 even if it's 8.1.

When the issue happens again, please share the output with this command "ps aux | grep php", if you hit the PHP maximum/children limit, try "killall lsphp" and you should be able to log in to WordPress. You can also empty the value of Memory Soft Limit/Memory Hard Limit /Process Soft Limit...

OpenLiteSpeed supports Server Name Indication (SNI), allowing users to set SSL certificates at the virtual host level. See https://docs.openlitespeed.org/configuration#set-up-ssl-for-virtual-hosts for more information.

It seems working for me. https://wkb.computerhuys.nl/ returns "Hello New World! From OpenLiteSpeed NodeJS".

I did a quick test, with/without LSCache rules, and with/without custom cache rules, but no luck. If it's still happening, could you create a ticket to support@litespeedtech.com with this forum post appended for further checking?

Thanks for the report. May I know the cache entries you reported? I tried the default LSCache settings but it works fine with OLS v1.7.19. May I also ask if you see any similar errors (pCache is NULL, pInfo is 0x57e58c8, pReq is 0x57e5248, pPath is (nil).) in the error log...

Like, how to generate that error, by visiting a specific page or any page? Does that error kee showing? Is that page served by the cache?

Hi @hp2 and @sbmg18 , I tried a lot but no success to reproduce the issue. If it's still happening, could you create a ticket to support@litespeedtech.com for further check?

If the duplicate socket causes it, remove it with the following command, then restarting LSWS. rm -rf /tmp/lshttpd/* systemctl restart lsws If it does not work, the issue is something else. Maybe hit the PHP maximum limit, PHP code looping ..etc/ Let us know how it goes.