Search results

Hi, Those rules should be generated by WordPress. Could you go to WordPress admin page > Settings > Permalinks, just click the Save Changes button and see how it works? It might be due to a permission issue if the rules are still not show.

No plan for uwsgi, but it should be possible to connect to the remote lswsgi process using TCP. lswsgi uses LSAPI protocol, server-side need to configures a remote LSAPI application. I will schedule a time to give this scenario a try.

Thanks for the report, I guess you created the virtual host from the vhsetup script, it's a bug, confirmed and fixed. For the existing log error, please go to web admin > Virtual Hosts > DOMAIN_NAME > Log, and edit Virtual Host Log File Name from "/logs/.error_log " to...

OpenliteSpeed Web Admin port will not accept 80/443 even you have a different network. If changing the firewall is impossible, then you might want to consider to set up a reverse proxy for the web admin which sounds weird to me through :ROFLMAO:

Hi, What are the Customized Error Pages settings on OLS Web Admin? Does it work if you visit the error page directly?

Depends on your vhost location, here's just a default Example virtual host config location, /usr/local/lsws/conf/vhosts/Example/vhconf.conf

Hi, Please use WSGI protocol with OpenLiteSpeed, check wiki here, https://openlitespeed.org/kb/python-wsgi-applications/#HowtosetupforDjango Best, Eric

Hi, If the site's redirect is done by .htaccess or OpenLiteSpeed rewrite, then you can of course change it from the SSH console. :)

Hi, Port 80 and 443 are more for the regular HTTP and HTTPS listener set up, please avoid to use it on the web admin listener.

@vpsingh It works now for me, could you try it again?

Thanks for the report, it might be due to some recent/ongoing AWS service issues. We will keep an eye on it.

I was trying to install weblate app but not successful due to too many package dependency errors. If you are still not able to figure it out, please raise a ticket to support@litespeedtech.com so we can help to check on the OpenLiteSpeed part.

How about <IfModule litespeed> CacheLookup on RewriteEngine On RewriteCond %{REQUEST_URI} !/company/list [NC] RewriteRule .* - [E=cache-control:max-age=120] </IfModule> <IfModule mod_rewrite.c> <IfModule mod_negotiation.c> Options -MultiViews -Indexes </IfModule> RewriteEngine On # Handle...

It works on my site. Did you put the rule on the top of the .htaccess file and restart the webserver? If so, could you provide the content of the .htaccess and site URL?

It's better to make sure that the environment works for the default Django project first, then start migrating the project you want.

mhm, may I confirm that the original Django + venv works fine and it starts showing 500 errors after you migrate the Weblate project?

Looks not right to me, wa is high, and there's no PHP process. Is it a fresh set up server? Since I can not reproduce it on my test server, could you raise a ticket to support@litespeedtech.com with the forum post link attached?

1. That is correct. Subprocess will run as the defined user and group. 2. Looks good to me.

Check an example here, https://docs.litespeedtech.com/lscache/noplugin/installation/#basic-rewrite-rules Hope it helps.

Hi, Could you please try to bypass any CDN and proxy first, then check the top command output from SSH while accessing the WordPress Startpage with a logged-in user?