Got it going but not well...
phpswitcher - deactivated - reactivated... seemed to help -
was getting 503 errors some still present but unable to get php switcher to show per_site mode even though the panel is setup in per_site... think its a db issue now...
?!? maybe not... maybe just me!..;p
Ran into an issue - not sure you've seen this potential issue...
phpswitcher - but per_site tried a reconfigure and issues are now abound due to higher MYSQL it looks like...
looking at re-configure from updated version to see if that helps..
Noticed recently don't have per_site php control any more..
not sure when I messed this up.
have several domain alias' as well as sub-domains - none of them show up in the switcher..
only the Top Level Domain... all others end up using server default of 7.1 it appears...
but I do have a few guesses and its been awhile..
betting specifically when I updated the mysql to a higher version....
patched 1.5.3 version... guessing this is part of the issue...
php currently adding via sury and have up to 8.1 showing in switcher working fine..
however...
wanted to verify per_site setting was correct...
so ran..
cd /var/www/imscp/engine/setup
perl /var/www/imscp/engine/setup/imscp-reconfigure -dar php
---
since all doku info sites are offline.. hoping that was right..
site is setup as per_site..
but get errors on front end update:
Package::FrontEnd::_setupMasterAdmin: DBD::MariaDB::db do failed: Duplicate entry '10' for key 'user_id' at /var/www/imscp/engine/setup/../PerlLib/Package/FrontEnd.pm line 1641.
---------
Sites Offline \ Panel offline -
Rebooted - Panel back online again -
PHP Switcher still no go for other domains
Sites not happy... (php sites all have 500 errors)
Whoops
---------
Ideas?
Perfect
Will give me an excuse to update
Where would that patched version be?
yes Still needed...
I can start the upgrade to Buster - that should be possible - have just held back due to other updates being a bit risky in the past... but I'm game.
What is the best way to move from existing on Deb 9 to at least 10.3/10.4 don't have to go up to 10.5 just starting to hit some packages that will require it.
Existing Package:
MariaDB 5.5.5-10.1.48-MariaDB-0+deb9u2.
i-MSCP 1.5.3
Build: 2018120800
Reviewing -
Not working I-mscp 1.5.3 install on Debian 9.13
Also got php8 updated via edits to phpmyswitcher... via post from fulltilt
Excellent!
finally got around to doing this..
ran the ssh only - will edit phpmysql next
thanks for the info - even if I waited 30 days to get it going!
excellent point..
-----------
reviewing this:
------------
So....
if that is an option I'd love to do that!
the only choice is force retry...
so domain overview > Manage SSL Cert > goes directly back to letsencrypt
I expect I'll need to somehow remove something via ssh to reset back to no ssl and start over...
Php Switcher - working fine
Except
What would the process be for php8 and registering that correctly - it is supported?
perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl --register --packaged
this is the command used in the past to register installed versions - would that still work and just add the path?
Using of course the sury method and just registering the installed PHP version that is maintained via apt vs manually building updates.
-----
Next Lets Encrypt
installed the update but have a few that are in an error state
An unexpected error occurred:
The client lacks sufficient authorization :: Certificate is expired
Please see the logfiles in /var/log/letsencrypt for more details. at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 896.
...propagated at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 899.
--------------
Admittedly I did not research the error more closely - not a major issue just yet - and expect its because I didn't update to the latest LE plugin in time for V2 to take effect.
---------
Deb 9CP
i-MSCP 1.5.3
Build: 2018120800
