Search results

If it's due to some spike traffic and the server does not have enough resources to handle it, then you could try to check the access log and mitigate it.

That is for the OpenLiteSpeed Web Admin, we have upgraded the PHP version for Debian, and it should be soon for the rpm system.

Check the error and stderr logs and see if there's any idle or hitting max PHP connection limit issues.

No problem, happy to help.

Hi @DonSYS91 Setup Example socket and start it. This is what I have tried, setup an example site by following some online posts server.js const WebSocket = require('ws'); const server = new WebSocket.Server({ port: 8080 }); server.on('connection', (socket) => { console.log('Client...

You might want to check if you have set up the domain mapping, and if the file exists in the document root.

Not sure yet, might need to debug. If you found a method to reproduce it, please send the issue with this forum post link to support@litespeedtech.com.

Please check if you have openlitespeed package installed or if it's got removed.

Hi, I tried a fresh setup with AlmaLinux 9, but was not able to reproduce the issue. What if you move the /dev/shm /dev/shm.bk, then restart the web server and see if it is able to fix the issue.

Assume you have the correct setup, but I don't think email works that way, maybe it uses a protocol other than HTTP/HTTPS, but I am not sure. Maybe other people in this forum can provide some other ideas.

What's the output of "ll /dev/shm/" and "ll /dev/shm/ols/"

To get Drupal admin access, please check https://docs.litespeedtech.com/cloud/images/drupal/#web-server-control-panel-access You can also get the admin URL and other info from the SSH pop-up message. Let me know if you have any questions.

Even though this is an old post, you may want to give it a try.

There's no plan for updating end-of-life PHP packages.

@stevieosaurus, for your information, the OLS dev team will add this feature but no ETA. :)

Follow https://docs.litespeedtech.com/lscache/lscwp/troubleshoot/#cache-purges-too-frequently to enable the debug log and see if it is caused by the auto purge. If not, then you might want to check if there's any corn job on the system to clean up the cache folder.

Docker Compose is a tool for defining and running multi-container applications. So in that stack, OLS, MariaDB, phpmyadmin, redis are separated. See https://github.com/litespeedtech/ols-docker-env/blob/master/docker-compose.yml Would I be correct in assuming that adding virtual hosts in OLS...

Since you already have a revere proxy, both method works. FYI, not sure if you are aware of the OLS + Wordpress docker compose solution, the stack would be simpler.

Thanks, will forward your feature request to the LiteSpeed team.

ok, you can post here if a similar issue happens again, or if you found the root cause.