Search results

That's a known warning, please ignore it for now, it should not cause any issues.

Thanks, I will forward it to the package build master.

Please check lsrestat.log, to get some idea of what happened. A graceful restart must be completed before issuing another one. 1. Avoid using systemctl stop lsws or systemctl start lsws, use Always use "systemctl restart lsws" only, otherwise it may break the graceful restart. 2. Avoid...

My OLS WP docker test server works fine with QC. Maybe something blocked the API in your stack. For further help with the QUIC.cloud, please raise a ticket on https://quic.cloud/support

Thanks, I don't see any symbolic links(the ln command should generate a link for it). Like this cgi-bin -> /usr/lib/cgi-bin

What's the output with the following command, ls -al /home/example.com/public_html/

I think this part is purely a WordPress configuration issue, and not caused by OpenLiteSpeed. Here's another guide that you might want to take a look at and see if it's easier to config...

I am a little bit confused, you are using nginx to serve wordpress already, so why and how to use ols-docker-env solution with the existing stack? Have you checked the .htaccess file? What's the .htaccess content?

Try full stop, then start OLS, and see if it helps. /usr/local/lsws/bin/lswsctrl stop systemctl restart lsws

Does the issue happen after changing the PHP version or something?

The "group" depends on your web server settings.

No problem

No problem, glad to help.

Because it's a template virtual host, web server doesn't know which virtual host you want to create and where to create, so you need to create the file manually. In my test, I'd put $SERVER_ROOT/conf/vhosts/$VH_NAME/.htpass to the User DB Location. Then you can go to the SSH console and...

1. Try to go to Virtual Hosts> General, and set $VH_ROOT to the Document Root. 2. If the subdomain also share the same document root, and no special rewrite for it, then you can add the subdomain to the same virtual host mapping.

As I said before, if you launch the server from the template, the lswsgi should be configured by default, have you contacted their support team regarding it?

@gui2one you need to replace the "VERSION" with a real number, e.g. 2.1. So the curl command will be like this curl -O http://www.litespeedtech.com/packages/lsapi/wsgi-lsapi-2.1.tgz

To configure LSWSGI, you can follow https://openlitespeed.org/kb/python-wsgi-applications/ But it should be working by default if you launch the OLS Django template from Hostinger.

Hi, I guess you are talking about LSCacheplugin integration, please raise a new issue on the LSCache Github.

Depends on the traffic, if it hits the limit, then you can increase it from e.g. 10 to 30.