Search results

I assume you want to use the app server from the OLS context, then please check https://docs.litespeedtech.com/cloud/images/nodejs/#how-do-i-use-an-express-app-on-this-image, let us know if it works.

Hi, I think the recaptcha rewrite method only support with LSWS but OLS. More, https://docs.litespeedtech.com/lsws/recaptcha/

Hi, I think the client/device will choose to use strong cipher by default, and we can still serve the device which only supports weak cipher. If you want to get rid of the 128, please specify the cipher you need.

I guess what @zoddshop means is, if the client/device supports both IPv4&IPv6, then the connection will try to use IPv4. If your client only supports IPv6, then I don't think it will cause any issues.

1. Yes, on the existing HTTPS listener 2. I think they use o.lencr.org, check https://letsencrypt.org/docs/lencr.org/ for more information.

From certbot guide security: Security parameters & server settings --rsa-key-size N Size of the RSA key. (default: 2048)

1. I don't think so. 2. Currently, no. 3. That script is for Apache mainly, you will need to remove all Apache part and update it to OLS. Or, run the script and make sure everything works, then replace Apache by OLS. with manually configuration.

Turns out it was due to 7G firewall rules. Disable the 7G rules and the request passes.

Then it should verify it. Could you DM me the test link?

Please try enabling reCatpcha function, https://openlitespeed.org/kb/recaptcha-with-openlitespeed/, or Add context for wp-login.php and xmlrpc.php, set deny to all and allow your IP only.

Hi, For FreeBSD, please follow https://openlitespeed.org/kb/install-openlitespeed-from-source-with-build-script/ to install OLS from source code.

Thanks for the report, issue is confirmed, will forward it internally.

For the performance part, I'd recommend fine-tuning the PHP since OLS does not support ESI. If you have LSWS, then you could use the cache plugin to speed up the site, see https://litespeedtech.com/products/cache-plugins/prestashop-acceleration. In case you might need, here's the guide for...

Glad to know you have it fixed.

Good to know you have it works~

Hi all, Please make sure the SSL is set on the both listener and virtual host level, you can not leave listener SSL empty, otherwise, the HTTPS listener won't work. Any SSL set on the virtual host level will overwrite it. More...

Hi, You may still need to put any cert on the listener in order to have the HTTPS works, then the cert applied on the virtual host level will overwrite it. If you still have the issue, please share the config here, or tag me @Eric from the golitespeed community on slack

Oh, I see what you mean. When those bot requests not hitting any virtual host and got an OLS 404 response, it should not cause any server load issue. If you still want to stop it, maybe you can try to create a virtual host with IP on domain mapping, then set deny to all in the rewrite rules. For...

May I know if you have an index file enabled on OpenLiteSpeed?

If you visit the site_url/loaderio-xxx.txt, does it loadable on the browser?