Search results

Did you launch the server from the marketplace? For the first time setup, use the pop up script to setup is the easiest method https://docs.litespeedtech.com/cloud/images/wordpress/#step-3

HI, May I know if you have followed this https://github.com/litespeedtech/ls-cloud-image/wiki/Build-WordPress-Image#what-if-i-want-to-use-it-directly to setup?

No, only LSWS v6+ supports this feature.

When you do "pecl install pdo_sqlsrv", did you see any error? Also, please "killall -9 lsphp" to make settings take effect. Let us know if it's still does not working.

Try this https://docs.litespeedtech.com/cloud/images/wordpress/#change-group

Replied on ticket

Hi May I confirm with you the web server is OpenLiteSpeed or LiteSpeed? If the issue is reproducible, please share to support@litespeedtech.com so we can take a further look.

Hi, it should. And I just updated the above command.

Check this https://openlitespeed.org/kb/setup-per-directory-file-php/

You can add context to your virtual host configuration like so context /forum/ { location /www/wwwroot/mydomain.com/forum/ allowBrowse 1 indexFiles index.php accessControl { allow * } rewrite { enable...

How about apt-get update apt-get upgrade openlitespeed and what is the current OLS version you have?

Sure, https://docs.openlitespeed.org/configuration#set-up-listeners

The custom error page supports on virtual host level only, so you might also want to do the same to other virtual hosts.

I see, but the 22% CPU usage is not really high actually. What's the output of the `top` command from console.

Is it normal traffic or it's unusual? If it's an attack, try setup Recaptcha or throttling to stop the attack, https://docs.openlitespeed.org/docs/advanced/security

Cool, thanks for the details. (y)

I don't see an issue with the config yet. Did you change any settings or upgrade any package recently?

Not sure if this is the same case as yours, https://stackoverflow.com/questions/22738196/permission-denied-publickey-when-pushing-commit-to-amazon-ec2

If you think it's not permission-related, then you might want to check the folder size, as well as the tmp folder.

What if you try to restart the lswsgi process? killall lswsgi Does any error show in logs? tail -f /usr/local/lsws/logs/*