It looks like the answer is "that's how it is". Undocumented breaking change.
I'll just keep editing the index.php because trying to get browsers to accept self-signed certificates is a pain.
I have a CentOS 7 dev server for older PHP versions running OpenLiteSpeed 1.7.19 which does not have this issue. The relevant section in $SERVER_ROOT/admin/html.open/login.php in that version is:
$is_https = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on'));
if...
$SERVER_ROOT/admin/conf/webadmin.key and $SERVER_ROOT/admin/conf/webadmin.crt both exist, dated 12th May 2025.
In WebAdmin Settings > Listeners > adminListener > SSL the Private Key File and Certificate File are set to the paths above, Client Verification is set to "none" and everything else is...
My server has recently updated to version 1.9.0 and I now get "Require https for admin panel." at the login page.
Because this is a local development system it doesn't have an SSL (not even a self-signed one), so if I try to use https I get a browser error reporting...
killall lsphp sorted it. imap wasn't showing in phpinfo() before and is after.
I'm pleased it was something simple that I missed my end. I'll add that command to my notes.
Feel free to move this form bug reports to somewhere more appropriate.
Thank you,
Paul
Hello,
I have installed lsphp84-pecl-imap and lsphp85-pecl-imap and restarted lsws, however the various imap_ functions (listed here https://www.php.net/manual/en/ref.imap.php) are not available in the relevant PHP versions.
Is this a bug or am I missing an important step somewhere?
If it's...
Hello,
After updating OpenLiteSpeed to 1.8.4 (from 1.8.3), logging into Web Admin failed - it just returned to login page with no error.
For each failed login it sent a "LiteSpeed Web Admin Console Failed Login Attempt" email.
During the update I noticed this message, which was the clue...
The older 8.x versions are just development steps to get the old code to 8.4. It's easier to go one version at a time and deal with those changes. New live code will be PHP 8.4.
That's exactly what I expected, thank you for confirming. Those folders make it easy to see what packages are available for different CentOS etc releases.
I will build a new development server running AlmaLinux 9 for PHP 8.0 onward and keep the current one for working with legacy code.
Thank...
I have a local development server (mini PC) currently running CentOS 7 with OpenLiteSpeed 1.7.19 and LSPHP versions 7.0 to 8.3. I am still supporting client websites running on various PHP 7.x versions hence the need for this setup (PHP 7.0 to 7.3 aren't available for newer distros).
Ongoing...
As attached screenshot, with OpenLiteSpeed 1.7.19 there is a stray \n in the top left corner of index pages. This maybe fixed in 1.8.0 which I know is imminent.
OK, it's sorted - so you can ignore this whole thread!
I had set the hostname to "dev" because it's a web dev server and I tend to use short names on my local network. However it seems that browsers look for .dev extensions and redirect them automatically to https. Even though "dev" != ".dev"...
I have now downloaded and compares the httpd_config.conf files from both servers.
The only differences are the serverName (expected), the memory limits for CGIRLimit (higher on the new one) and the memory limits for railsDefaults, wsgiDefaults and nodeDefaults (all 2047M on the old server and 0...
EDIT: OK, it's sorted, so you can ignore this whole thread! If an admin wants to delete it that's fine.
I have completed a fresh installation of OpenLiteSpeed with various PHP versions on CentOS 7 on physical hardware. This is set up the same as an existing installation also on CentOS 7 in...
I decided to stick with CentOS 7 in the end. Although lsphp70 is available in Ubuntu 18.04, several other parts such as lsphp70-gd and lsphp70-xml aren't, whereas they are for CentOS 7. Indeed even versions down to lsphp53 are available.
I did have a couple of issues with CentOS 7 on the...