Recent content by Cold-Egg

Yes, Jammy is Ubuntu 22.04.

@YouStable Pushed, please update the package, and it should support 14.4.0 now. See https://rpms.litespeedtech.com/debian/pool/main/jammy/

It's more like a PHP package-related question. For Debian, lsphp83 and 84 are using the ioncube 14.4.0 already. May I know how you installed the php package, and what's the current OS and version? FYI, if you need to stick with php81/82, then the minimum ionCube version is 12.0.1(PHP8.1) and...

The cache module should be installed and enabled by default. May I know which CMS you are using? Do you have any URL to verify the response headers?

Any config changes to the VHost Template will only affect all vhosts that use the template.

curl should work too. I just used curl to trigger the reCAPTCHA feature. Log: [RECAPTCHA] tries: 3, concurrent conns: 1 bot detected for vhost [Example], reason: FailedCaptchaVerify, close connection! You could use parameters like --parallel --parallel-max 10 and send it multiple times to...

Glad to know you have found the issue.

I mean, can you do something like `curl --resolve www.hanumaninstitute.com:5006:127.0.0.1 http://www.hanumaninstitute.com/blog/` from the host server?

OLS + WP should be a complete stack already, not sure why you want to add an additional layer? From the response header, as Nginx is doing the proxy, it's hard to tell if the redirect is made by Nginx or not. Have you tried to curl the blog domain locally with resolve 127.0.0.1:5006 and see if...

It would work if you used a virtual host template.

Hi, You could check https://wordpress.org/support/topic/litespeed-caching-creates-huge-caching-folder/ and verify if the huge cache files are caused by different query strings, bot, or user agents. Purge all will mark those caches as invalid, and will be removed by server after some time. To...

It could happen if there's an unusual service stopped due to e.g. OOM, or maybe the graceful restart was corrupted due to systemctl start lsws. Please try to use systemctl restart lsws instead and monitor it for a while and see how it goes.

Please navigate to SSL Listener > SSL, enable the Session Cache option, and see if that improves the situation. However, keep in mind that most modern browsers use session tickets instead, so enabling the session cache may have limited impact.

Is there any errors in /usr/local/lsws/logs/error.log happened during the"killed by signal: 1"?

The error is probably happening within this function https://github.com/litespeedtech/ls-cloud-image/blob/master/Setup/vhsetup.sh#L604-L618 Please check if you can run the wp command, and DB access is working.