Search results

Hi @metalsonic , Same issue to https://forum.openlitespeed.org/threads/fatal-python-error-py_initialize-unable-to-get-the-locale-encoding.4303/ ? I can reproduce it on CentOS 8 too. Debian system works fine. Will check it in more details, maybe it's env or venv issue.

LSPHP5x only support up to Ubuntu 16. For ubuntu 18, 20, please try lsphp7x

Hi @saz99 , You can also follow https://docs.litespeedtech.com/cloud/images/wordpress/#how-do-i-set-up-virtual-host-specific-php to setup PHP74. Next wordpress image update will has the PHP74 installed by default.

@highlander926 , The OLS access should be the same as CyberPanel access. Please visit CyberPanel > Firewall and allow port 7080, so you can access OLS panel.

Did not receive any similar case yet. May I know if you can search the package success from the server? Example for apt server, apt search lsphp56*

Hi, It's been a while, may I ask if the issue still exist?

Hi, Please check if your app support PHP73. If there's no PHP error, please raise a ticket with us support@litespeedtech.com Best, Eric

Hi @natas123 , Did you set any Per Client Throttling under security settings? I tried several times from my test server with both HTTP/HTTPS but no luck. Will DM you the site URL see if you can reproduce it easily. Best, Eric

Restart the "LiteSpeed web server" should has no down time, so no need to back up.

What's the out put ps aux | grep php

@propertyhomey Please try restarting web server see if it helps. systemctl restart lsws

Hi @Dolirow , You hit the limit somehow, please increase both number from 60 to e.g. 100 maxConns 60 env PHP_LSAPI_CHILDREN=60 Then restart the PHP by killall lsphp

I did not see any obvious issue from the screenshots, possible to submit a ticket to support@litespeedtech.com with this post link appended?

This is the current latest stable release, which version you want to upgrade? You can use lsup method to upgrade to 1.7 if you want. https://openlitespeed.org/kb/how-to-upgrade-openlitespeed/#Method_2_lsupsh_Script

Just saw your same question on Slack and it got resolved .

Usually it's due to something else is listening on the same port. Can you try netstat tool to check again, e.g. netstat -antupl | grep 443

Maybe it's a setting issue. Possible to provide screenshots of listener and vhost settings?

If you install from ols1clk script on Ubuntu 20, then the default version is 74

Log shows STDERR on Aq_Resize.process, if this is your test server, possible to disable the Aq_Resize.process and see if issue gone?

Hi, Even if you don't apply rewrite rules, keep-alive is still enabled by default on OLS, so your presumption might be wrong. About 404, please remove the GCP Load Balancer and check if the issue still reproducible.