Recent content by Cold-Egg

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.

I can't reproduce the issue locally, could you raise a new ticket to support@litespeedtech.com with this forum post link appended? We will help to check the issue further from there.

We haven’t received any other similar reports. Could you please email the issue to support@litespeedtech.com and include a link to this forum post? We'll continue investigating from there.

I just installed OLS on RoxyLinux 10 without any issues. Maybe you can back up lsws folder just in case, and then install the OLS again and see if there's any error in the middle. Or manually setup the service file "/usr/lib/systemd/system/lshttpd.service" # should be added as...

Will forward the issue to the dev team

The real service name is lshttpd So you can either use this service lsws status Redirecting to /bin/systemctl status lsws.service ● lshttpd.service - OpenLiteSpeed HTTP Server Loaded: loaded (/usr/lib/systemd/system/lshttpd.service; enabled; preset: disabled) Active: active...

In theory, yes, because I did not manually build it on a CentOS 8 ARM server before. It’s also possible to install LSAPI PHP (lsphp) and MariaDB manually instead of using the ols1clk script.

@hp2 Our dev team has updated the release package(same version) on GitHub now, could you please try it again?

Thanks for the report. The `always` is supported and is the default value. onsuccess is not. I will forward this to the dev team.

@xirtam Could you let us know the output of this command? /usr/local/lsws/bin/lshttpd -v In addition, please try running the following command to update to the latest package build and see if that fixes the issue: /usr/local/lsws/admin/misc/lsup.sh

@xirtam Could you let us know the output of this command? /usr/local/lsws/bin/lshttpd -v In addition, please try running the following command to update to the latest package build and see if that fixes the issue: /usr/local/lsws/admin/misc/lsup.sh

1.8.5 has been repacked before, so if you haven't, could you try lsup again?