Search results

@imon Please check the list, as you can see there's no php74 for Noble. Jammy https://rpms.litespeedtech.com/debian/pool/main/jammy/ Noble https://rpms.litespeedtech.com/debian/pool/main/noble/

The packages you mentioned should still be available for the Ubuntu 22.04 arm64 system, please confirm once more. As for Ubuntu 24.04, there has never been an lsphp74-* build available.

Sure, TLS 1.1 will be set to Off by default on the next release

We will check the browser compatibility first, then decide it.

Follow this doc should work. If the issue is still happening, please share the config file.

Open the browser dev tool, check the Location header and see if WordPress redirects it.

Well, the repo package for OLS v1.8.3 is not even ready yet. If you use lsup to upgrade to v1.8.3, then you can use dnf to upgrade it to the next release once, e.g., v1.8.4 is released.

If you install the package from the litespeed repo by following https://docs.openlitespeed.org/config/php/#prerequisites, then it should work. Maybe you could try the apt package method and let us know how it goes.

Hi, For LSCWP-related issue, please help to post it on the LSCache for WordPress support forum!

Please try to restart the php process and see if it helps. https://docs.openlitespeed.org/config/php/detached/#stop-all-immediately

Check the package list here: https://rpms.litespeedtech.com/debian/pool/main/noble/. As you can see, the oldest PHP package available for Ubuntu 24.04 on LS repo list is version 8.1. You may want to upgrade the site to support PHP 8, or you could try building PHP 7 on Ubuntu 24.04 yourself, but...

You might also want to consider using some free control panels with OpenLiteSpeed, as they automatically create a Linux user:group for each account and enable PHP suEXEC by default, offering enhanced security.

If you installed the OLS v1.8.3 Debian package on the Ubuntu/Debian server, it should depend on php 8.3, and the 7.4 can be removed. Have you verified which URL or in which case you triggered the "PHP Warning"?

That should be included through. You can also consider implementing suEXEC, but this may not work if all the accounts run as the same Linux user&group. You might also want to check if open_basedir helps or not in your case.

May I know if there's any control panel on the server? And, do you use the same user account for all the virtual hosts? Features like namespace can implement sandboxes to isolate files, users, processes from all others.

Does the warning happen when you visit OLS web admin? If the current OLS version/package depends on PHP 7.4, you might want to keep it.

Could you share the phpmyadmin URL or a screenshot of the issue?

It should work, could you share the command you applied and the server config here or Inbox me the information?

In the future, maybe you can consider to setup an OpenliteSpeed to handle the https and websites without a proxy. The force www and SSL can be done by the following rewriterules. RewriteCond %{HTTPS} off [OR] RewriteCond %{HTTP_HOST} !^www. RewriteRule ^(.*)$ https://www.example.com/$1...

Glad to know you have found the issue. We can keep it, in case other users hit the same issue.