Search results

https://forum.openlitespeed.org/threads/mcrypt.4955/#post-11227 @a159cm , if not working, please share the error output

LSCache won't cache static files. LSWS/OLS has both gzip and brotli enabled by default, so no need to change it. You can verify it from your browser tool.

Not sure if you want to use edge certificate or client certificate. You can upload your own key/cert to the server, and point either Listener>SSL or Virtual Hosts > xxxx > SSL, to load it from the web admin. https://docs.litespeedtech.com/cloud/images/wordpress/#step-4-set-ssl-for-https

You can do phpinfo comparison between Apache and LSWS, see if their memory size is different. Increase: Web admin > Server Configuration -> External App -> lsphp Process Soft Limit Process Hard Limit Also, increase the memory limit from php.ini

We can install mcrypt package from pecl, https://docs.litespeedtech.com/extapp/php/extensions/#configure. apt-get install lsphp74-pear -y apt install lsphp74-dev libmcrypt-dev -y sudo /usr/local/lsws/lsphp74/bin/pecl install mcrypt add extension=mcrypt.so to...

Resolved by turning on compression in phpmyadmin

Maybe it has something to do with the PHP limit. Can you try to increase both Memory Limit and Process Limit to the lsphp?

I am not sure the root cause, but it seems like a server resource issue to me https://forum.image.sc/t/jvm-error-could-not-allocate-metaspace-solved/12543

with this post link appended should be ok, we may ask for more information via ticket

Could you raise a ticket to bug@litespeedtech.com for further support?

/usr/local/lsws/admin/misc/lsup.sh -v 1.7.12

@stmx Just so you know that OpenLiteSpeed v1.7.12 has this issue fixed, feel free to give it a try.

18.168.235.88 can not be reached. Do you want to allow the domain only? if so, visit the web admin at port 7080 > Listener, make sure you have the domain mapping only.

Hi, We support the long-term support version, so the next one will be 22.04.

If you have an SSH key added to the Metadata>SSH Keys before or after server launching, should all works. To run the ufw command, please run as root. You can try sudo ufw allow 7080 or sudo -s, then rum the ufw command again.

Hi, My guess for 403 works is because it won't hit the following rules. Whereas, ID 112 hit this. RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.+)$ index.php?page=$1 [QSA] Maybe this cms has a build-in 404 page somewhere, so it redirected...

Should be Access-Control-Allow-Origin * instead of Access-Control-Allow-Origin

Hi, Please check https://openlitespeed.org/kb/setting-up-cors-on-openlitespeed/ Add CORS extra header through OLS Context

I just did the same test, it seems like a bug on OpenLiteSpeed. Will update you once we fixed it. In the meantime, please try to turn on the LSCache, reCaptcha, or Cloudflare under attack mode.

Hi, Could you try a simple one first, e.g. RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ https://example.com/ [L] and make sure it's works. Or turn on the rewrite log and make sure the request goes through the rewrite.