Search results

For OLS, I don't think there's a way to bypass a directory. Have you tried to disable that single rule only and not the whole modsecurity service?

What if you upgrade to v1.7.18, does the issue happen as well?

The existing LS package with PHP 70 is on Ubuntu 18.04, see https://rpms.litespeedtech.com/debian/pool/main/bionic/. Building PHP70 on a newer system is possible but difficult since many dependency packages are not allowed to be compatible with the old version.

Hi, Those logs do not mention the root cause, please submit a ticket to support@litespeedtech.com with this forum post appended for direct help.

That might be a different issue. Please check the log and server load to see which process or service uses the most resources, and if the server is under attack.

It might be easier if you check the error log, locate the rule ID, and then whitelist it or comment out the rule.

1. The OLS Docker container uses the Virtual host template by default, so you might want to configure it manually. 2. My guess is, to let ALB take care of the HTTP/HTTPS, and your back-end service connection via HTTP only. Note, that you might need to overcome the cache problem for multiple...

That could be the reason, you can also check the throttling settings. If it's reproducible, you can submit the issue to support@litespeedtech.com with this forum post link appended.

Thanks for the information. If you request any static files, e.g. css, images, do those have a delayed response? If so, it's possibly due to the security settings. If not, then you might want to check the PHP settings.

OpenLiteSpeed package only supports LTS, please install it on Ubuntu 22.04.

If possible, could you share the output of the `top` command and see if it's a server load issue?

Sure, removed.

Is it a shared server? Maybe it's controlled by the hosting manager. Since it's a shared server, you probably have no permission to check the configuration.

I meant the certificate setup is correct. The certificate won't match the IP, you need to fix that redirect issue from WordPress. REMOVED

Hi, I checked the config, and it looks good. The issue is probably that your WordPress URL or Home URL is set to the server IP, so the domain redirects to the IP address, and the certificate does not match the domain so it is shown as insecure.

Could you share the config file so we can take a look? You can Inbox me if you don't want to share it in public.

It's possible, but it may not be compatible with LSCache since the load balancer does not recognize the cache tag and purge request. If you still want to keep the load balancer, another method is to implement the QUIC Cloud CDN, so the cache files will be stored on the CDN/edge nodes.

Duplicated post, so closed

No problem.

Hi @williamskea, I saw you have posted similar questions in many places, so I will just reply here once. The current system's default version is v6.9, to get v7.0 with the Imagick package, you will need to compile it. wget...