Search results

If you want to use OpenLiteSpeed, then v1.7.19 is the current stable release. To use v1.8.x, you can either upgrade via lsup command or download from the source since it's not marked as stable tier yet. To get more information for the update, please check openlitespeed on github.

Will update you here once the package is ready.

I tried Mautic a while ago and it was working fine. If you visit a static file, does it return a 200 status code? If everything returns a 404, then it's possibly an OLS configuration issue.

@rahulsoni Could you provide the OS and PHP version? I will try to check on that first.

If it's a WordPress, you can update and customize the permalink to achieve it. If not, check this post method.

For this case, you might want to check this install-le-on-test-server-before-making-the-site-live post. If apply cert is successful but failed on OLS, then you can post the OLS configuration here so we can have another look.

Hi @Andriusa Please check a similar post here.

If the site can apply LSCache, then you don't need the Pagespeed module, it may conflict with LSCache. May I know what CMS you are using? Please check if disabling the pagespeed module helps or not. Check https://docs.litespeedtech.com/lsadc/moresettings/#pagespeed for more information.

@datverse Packages are pushed, feel free to give it a try.

Hi, Since you built your own OLS and PHP, it might due to the permission issue somewhere. If you have another VPS, please install OLS from LiteSpeed repo and compare the folder & file permissions.

For example, /bin/bash <( curl -sk https://raw.githubusercontent.com/litespeedtech/ls-cloud-image/master/Setup/vhsetup.sh ) --delete www.example.com

modsecurity + OWASP should not cause the lsws process stopped to work. For the newer modsecurity module, better to wait OLS release it. To disable it, use the following command: bash <( curl -k https://raw.githubusercontent.com/litespeedtech/ols1clk/master/ols1clk.sh ) --owasp-disable

Good to know you have found the root cause.

Please make sure you trigger the ban via 3rd server or device, otherwise, you may lose the connection and not be able to check the .rtreport and server error log. If you can still reproduce it, please submit the issue to support@litespeedtech.com with this forum post link appended.

We may consider sharing it on GitHub once it's organized but no ETA. The easiest method for you is to update existing OLS with the following command, /usr/local/lsws/admin/misc/lsup.sh -v 1.8.1

Hi @mister_x It works from my test. When OLS bans an IP, you can run the following command to check it. grep BLOCKED_IP /tmp/lshttpd/.rtreport* You felt the banned IP was not getting released, maybe it hit the limit again. Please check the error log, it should show something like "Reached per...

Do you mean that you have another service running on the same server, and you set a web server External Application for it? It sounds right to me. More https://docs.openlitespeed.org/docs/advanced/proxy#create-a-web-server-external-application Maybe you can describe the event in more details...

Try to restart the PHP with `killall lsphp` command and see if it helps. If not work, please try adding rewrite to no abort by following https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#php-without-timeout

The ModSecurity module with OLS is probably optimized. Check https://openlitespeed.org/kb/openlitespeed-modsecurity-module/ if you want to reinstall the module or setup OWASP CRS, there should be no special settings for it.

If you have a virtual host for that IP, then you can add the cert to the virtual host > SSL. See https://docs.openlitespeed.org/configuration#set-up-ssl-for-virtual-hosts