Recent content by Cold-Egg

I will forward it to the dev team and see if we can include this request in the next release.

This finding refers to TLS 1.2 signature hash alg with OpenSSL. Modern clients will negotiate SHA-256 where supported. SHA-1 is only present for legacy compatibility and is not actively used in modern handshakes. Currently, OpenLiteSpeed does not offer such a configuration. If you really need...

You're welcome. The reason is that the newer OLS version runs PHP in detached mode, so you need to reload PHP whenever you add a new module or make changes to php.ini.

Forwarded to the dev team, we will enhance this part, thanks for the report.

Do you see imap package in the phpinfo? If not, restart the PHP process (killall lsphp) You can also try listing the imap functions with <?php print_r(get_extension_funcs("imap"));

@wassupdev 1.9.0 package was pushed yesterday.

For a WordPress site, please remember to use the LSCache plugin for WordPress to manage caching instead of relying on cache rules or policies. As for PHP tuning, it largely depends on your environment and traffic levels. There isn't a one-size-fits-all configuration. If your site isn't showing...

The OLS repo package will be built and pushed weekly, so you may expect the package sometime this week. For now, to use the latest version, try /usr/local/lsws/admin/misc/lsup.sh command in the SSH console.

To do this you would have to click the "details" button in the bottom right and then a little link will say something along the lines as "continue to (website) anyway (unsafe)". If it does not work, do you have any screenshots?

Thanks for the report. We’ve rebuilt the package which should includes a few minor bug fixes, and republished it with the same version number. If you install the package from litespeed repo, justupgrade the package should do it, e.g. `apt update && apt install --only-upgrade openlitespeed -y`

Hi @xirtam For further modsec with a custom error code on LSWS, please post in the LSWS forum. Thank you.

Thanks for the report, will check it further via the support ticket.

I'm a little confused. If the / context is already proxying everything to vaultwarden_backend, and you want to add another context for /admin to whitelist specific IPs, is that correct? If so, you may want to use another proxy context rather than a static context.

Do you mean /empty/admin is a folder? Then /admin/ is expected. If that's not the case, please provide more information, like is there any file under the admin folder.

Sorry for the typo.