Search results

The issue has been addressed and will push it to the next release.

Thanks, I can reproduce it now (need to visit any site to trigger it), will forward the issue to the LiteSpeed team.

Still no issue on a clean setup. May I know if those machines all have DirectAdmin installed? Could you share how you enable/disable the AIO mobile on your server?

I have tested OLS v1.8.1+ Ubuntu 22.04 + libaio1 without issue. I'm going to test it on AlamaLinux and get back to you.

Depending on which parameters you want to ask. For some settings, yes, but you might have different requirements for each virtual host, like SSL, document root, log path, ACL, security ..etc.

Hi, For OpenLiteSpeed, it only recognizes the rewrite in the .htaccess file. To disable the public cache lookup, you can add a cache module to your virtual host and set checkPublicCache to 0 (0 means disable). E.g. checkPrivateCache 1 checkPublicCache 0 maxCacheObjSize 10000000...

Updating files with root should be fine.

5 and 10 are way too small. If you just want to trigger the feature, the easiest way is to set the value 1 to Static Requests/second and Dynamic Requests/second, then visiting any page should get you a 403 error. To trigger the connection limit, you can use a benchmark tool or command to...

mhm, may I know if the openlitespeed service starts without any issues? Could be a permission issue somewhere. Better to create an addition topic for different issues.

I did not see any similar report, please submit the issue to support@litespeedtech.com with this forum post link appended for further help.

Do you mean the per-client throttling or PHP configuration?

Thanks for the report, the issue has been confirmed and will be addressed in v1.8.1.

You can configure port 80 with HTTPS, but it's not recommended. It could cause users to have to specify the port with HTTPS to use, and the certbot renewal may not work.

@rakoxsynt Did you change anything to the admin configuration? If so, please share the config files and the error log.

So it's not a TLS issue but an upload speed issue. Please create a ticket to support@litespeedtech.com with this forum post link appended. Once resolved, we can share the result here.

mmm, what about that startup file, does it help if you set a full path, .e.g. xxxx/dist/server.js? If it still does not work, please raise a ticket to support@litespeedtech.com with this forum post link appended.

Please raise a ticket to support@litespeedtech.com with this forum post link appended for further check.

Try this, and let us know if it works. rm -rf /dev/shm/ols service lsws restart

In case you might want it, here's the step to build the image, https://github.com/litespeedtech/ls-cloud-image/wiki/Build-WordPress-Image

Have you set up the virtual host domain mapping under the listener? See https://docs.openlitespeed.org/configuration#map-virtual-hosts