Search results

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.

Follow the doc, once you setup the external app, then you can set up the proxy with rewriterule. https://docs.openlitespeed.org/docs/advanced/proxy#method-1-proxying-with-rewrite-rules e.g. RewriteCond %{HTTPS} !=on REWRITERULE ^(.*)$ HTTP://p1/$1 [P,L,E=PROXY-HOST:hm.mydomain.com ] RewriteRule...

My experience is, that when you create an OLS Django template + instance, it should be an instance from Hostinger instead of another VPS provider. The price depends on the server type/spec, 1$/day is probably a powerful server. As long as it is named OpenLiteSpeed, then it's the community...

1.8.x is not on the stable tier yet, once it is ready, we will build a package and push it to the repository. https://rpms.litespeedtech.com/centos/9/update/x86_64/RPMS/

HI, I think you just need to fix the SSL config on the port 8080 listener. If you want to use hn.mydomain.com in the front, and localhost:8080 at the backend, you can follow https://docs.openlitespeed.org/docs/advanced/proxy to setup reverse proxy.

Replied.

Maybe you changed the config permission by accident? Please submit the issue to support@litespeedtech.com with this forum post link appended.

@superipey I just ran the same command to install the package on a fresh server. The cache module is installed by default. So I am not sure why it does not exist on your server, maybe you can manually add the module by following https://openlitespeed.org/kb/litespeed-cache-on-openlitespeed/

Are you still at the login status? Is there any error shown in the server error log and admin error log(/usr/local/lsws/admin/logs/error.log)?