Search results

Hi, could you send the issue to support@litespeedtech.com, our dev will take a look from there.

Check https://forum.openlitespeed.org/threads/aio-is-not-supported-on-this-machine.4053/, it seems not related

Maybe you can send the issue to support@litespeedtech.com with this post link appended so we can check further from there.

How about phpinfo page, does intl show on it?

That site is loading fine now, did you fix it?

Have you restart PHP by "killall lsphp"? maybe you can create a phpinfo page to verify if the package is installed or not first.

That should do it, maybe you have other rules at some other place? Might need to turn on the rewrite log and check it.

To narrow down the issue, you might want to turn on the rewrite log (set to 9) and see which rule got applied or skipped

When you have a valid cert with OLS, http/3 should be used by default. If you still have a configuration issue, feel free to join https://litespeedtech.com/slack and message me @eric from there, I can help to check the issue with you more quickly.

Maybe for LSWS, https://www.litespeedtech.com/support/forum/threads/litespeed-charset-problem.14549/ I saw you want to migrate site to OLS, since OLS does not support Apache modules and many custom rules in the .htaccess file, maybe you can try LSWS instead. ;)

Right, OLS does not support it.

"I first configured SSL on the normal site, but it didn't work, ", did you apply any certificate or upload any valid certificate? If there's no valid cert, then it will return the same result with a different HTTPS port listener. For 404 issue, did you put any domain value to the listener and...

I will forward the req to the team.

For OLS, you can set the header via Virtual Host > context > Header Operations, it may not check if it's empty or not. More example https://openlitespeed.org/kb/setting-up-cors-on-openlitespeed/

For OLS, you can set the header via Virtual Host > context > Header Operations More example https://openlitespeed.org/kb/setting-up-cors-on-openlitespeed/

It's not a bug, it is how you define the header. This is your current CSP from the header, content-security-policy: default-src https:; font-src https: data:; img-src https: data:; script-src https:; style-src https:; You might want to check...

No, but you can try the context feature with regular expression.

The cache seems working correctly. LSCache will be based on the URL, so, when you switch the URL, all cached files will be invalidated, that's why you saw the CPU spikes.

The context looks fine to me. I am not clear about how you set up the /httperror/404 page, it seems like you want to redirect to 404 by the App instead of the web server. If you want to custom OLS error page, please check https://openlitespeed.org/kb/custom-error-page/. About the 400 error, no...

May I know what is this CMS? If possible, please implement lscache to reduce the PHP process and MySQL load