Search results

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.

No global policy for that, but you could consider using the include file method and apply it to all the virtual hosts. https://docs.openlitespeed.org/config/advanced/includes/ For such general questions, please post it in general openlitespeed discussion thread.

Which operating system are you using? Is it Ubuntu 24.04? Please share the full installation command you ran and the exact error message you received.

mm. not sure, because it works even though I don't have that crb repo under the yum.repo.d folder at all.

LiteSpeed currently only supports offloading SSL and forwarding to the backend using ws://, not wss://. A similar discussion can be found here: https://forum.openlitespeed.org/threads/websocket-reverse-proxy-over-tls.5237/

Just an update. There have been some updates to the RPM packages, so I launched a fresh AlmaLinux 9 instance and was able to install all the lsphp82 and lsphp83 packages without any warnings."

Which control panel? if you set an virtual host access log path to, e.g. /home/username/logs/access.log, then the virtual host access log path is /home/username/logs/access.log. Please provide more details of the issue.

If so, please submit the issue to support@litespeedtech.com with this forum post link appended for further check

@eakteam Are there any sites experiencing this issue even without LSCWP installed?

I just did a quick test for OLS + OWASP, and the error log logs " [INFO] [146419] [1.2.3.4:59423:HTTP2-11#wordpress] [Module:mod_security] ModSecurity: Warning. Matched "Operato ..." as expected on both server and virtual host levels. So you might want to check if theLog Level has INFO included.

Thanks for the info. For LSCWP-related questions, feel free to open a post on https://wordpress.org/support/plugin/litespeed-cache/

It supports the virtual host level only, see https://docs.openlitespeed.org/security/headers/ If you want to reduce the duplicate set up, you could consider the virtual host template or include conf feature(https://docs.openlitespeed.org/config/advanced/includes/).

Not pretty sure as there's no similar report. If it's still happening or there's a reproduce method, please submit it to support@litespeedtech.com for further support.

For DirectAdmin, you might want to use their method. See https://forum.directadmin.com/threads/how-to-reverse-proxy-openlitespeed-on-directadmin-working-with-net-core-blazor.60218/ and https://docs.directadmin.com/webservices/openlitespeed/customizing-ols.html for more information.

According to Fail2Ban GitHub note, IPv6 support is implemented in version 0.10

Maybe something like fail2ban and CrawdSec may help. We added fail2ban to the ols1clk script a few days ago, and it's mainly to protect wp-login.php and xmlrpc.php from multiple POST requests. Feel free to adjust the fail2ban config to match your goal.

The default value is set to no limit. Please avoid changing this setting unless you're certain of its purpose. perClientConnLimit { staticReqPerSec 0 dynReqPerSec 0 outBandwidth 0 inBandwidth 0 softLimit 10000 hardLimit...

Those settings look fine. If this keeps happening, please submit the issue to support@litespeedtech.com for further assistance.