Search results

Hi, Not here, please raise a ticket to support@litespeedtech.com for the check.

May I know if the lsws process is still running when the issue happens? Could you try the last build of OLS and see if it makes any difference? /usr/local/lsws/admin/misc/lsup.sh -b -e 1.7.13 If it is still happening, please share some error log so we can help more, or you can send the log to...

Hi @sangroxx Should have nothing to change from OLS in order to login to the web admin, could you submit a ticket to support@litespeedtech.club with this forum post link appended so we can take a look?

May I clarify that the "CSF" service is running in the backend, and you can visit 127.0.01:xx successfully, now you want to put OLS in the front to do the proxy? Could you try Method 3: Proxying with Rewrite Rules from https://openlitespeed.org/kb/reverse-proxy-basics/ and let us know if it...

For LSWS, you can ask questions on https://www.litespeedtech.com/support/forum/ next time. "Activated the Litespeed Litespeed extension to use LiteSpeed", do you mean the LiteSpeed Web Server? if so, the answer is yes, you can just apply for a LiteSpeed license on the existing server...

yes in my opinion.

Need to check the log Did you have the same OLS version on both 18.04 and 20.04? Maybe you can raise a ticket to bug@litespeedtech.club so we can take a look for you.

PLease try to allow 7080 on firewall, sudo ufw allow 7080 https://docs.litespeedtech.com/cloud/images/wordpress/

How about creating another context for admin-ajax.php with no authentication?

Sure, please visit web admin at port 7080 and update the domain from the listener https://docs.litespeedtech.com/cloud/images/wordpress/#step-2-add-domain-to-listener

May I know if abc.com, and sub1.abc.com ..etc all from the WordPress multi-site? Did you set different virtual hosts for each domain including sub-domain? or you set it on the same virtual host? For the same virtual host case, maybe you can try to put a `*` on the listener and see if it helps.

Those should not cause 502 issue. We'd love to take a deeper look if you have seen this issue happens regularly or found out the reproducing method, please share the issue with support@litespeedtech.com.

Hi, May I know if there are more error logs?

Do you have any core files being generated in /tmp/lshttpd/bak_core during the 502?

If you put it on the bottom, OLS will stop when hitting any [L] tag. The L means the last rule in LiteSpeed. So it should be fine if you put it on the top.

Hi I think this KB should help https://openlitespeed.org/kb/lets-encrypt-ssl-on-openlitespeed/ Put the key on each virtual host > SSL is correct, you also need to make sure that listener has one cert on it. If still not working, please share the listener and VH mapping set up with us, either...

Yes, it is how it works by default. If you have Webp images and webp replacement enabled, then your browser will load WebP version when it is supported.

It means it's not OLS related questions, you might want to ask on serverfault.com or StackOverflow for more help.

Hi, It's an Apache server actually.

Someone asked recently how SlickStack WordPress compares to OpenLiteSpeed WordPress, so I ran this benchmark. The Result OpenLiteSpeed WordPress Stack performed 6X better than SlickStack when serving a cached WordPress site over HTTP/2. OLS WordPress Stack = 21669.93 Request per second...