Comments on Update the ISPConfig Perfect Server from Debian 10 to Debian 11

There is a need to update so you do the guide or is only to explain how to do if someone want to do it?

Thank you

There is no need to update. The Debian developers support Debian 10 with updates until June 2024.

There may be a need to upgrade f some websites needs PHP 7.4 or something needs the new kernel. So thank Till for this tutorial.

Sorry but : "Be aware that all websites on this server that use the PHP version "Default" will now use PHP 7.4 instead of the old version"

this is not working because , i've got a "502 bad getway error"

I found a solution to the problem collecting mail in a queue "connect to 127.0.0.1 [127.0.0.1]: 10026: Connection refused". amavisd-new configban (/etc/amavis/conf.d/20-debian_defaults): $inet_socket_port = [10024, 10026];$interface_policy{'10026'} = 'POLICYVALAMI';$policy_bank{'POLICYVALAMI'} = {   bypass_spam_checks_maps   => [1],   final_virus_destiny => D_PASS,   final_spam_destiny   => D_PASS,};

More and the source of the solution: https://hup.hu/node/174834

Hello Piotr, thank you for posting your workaround. The correct solution is different though and has been posted in the iSPConfig forum already a few days ago. I highly recommend that you undo your changes and follow the instruction that we posted here: https://www.howtoforge.com/community/threads/after-upgrading-from-buster-to-bullseye-problems-amavis.88528/#post-432778 to solve the issue.

With your workaround, your setup will likely stop working as soon as you install the next ISPConfig update.

Will you be updating this for debian 11? I see a lot has changed

This tutorial is up to date, nothing has changed since the guide has been written as this guide is for Debian 11 as the target system. And Debian 12 does not exist yet, so a tutorial for updating Debian 11 to Debian 12 can't exist yet.

You didn't say how to make phpMyAdmin use the default PHP 7.4 version. As of now, even after upgrading, phpMyAdmin shows v7.3. Even after restarting Apache2.

phpmyadmin: $cfg['TempDir'] = '/var/lib/phpmyadmin/tmp'; is not accessible

It shows such an error, changing permissions does not help.

I have installed it from scratch several times, same error every time.

Anyone knows the solution to this problem?

After upgrade, postfix cant work well. in webmin / servers / postfix / smtp client's limited its show: This map cannot be edited : Failed to query table : You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'from where = limit 1' at line 1.

The same notification is show under other 'icons' under webmin postfix, when the *.cf files are filled in some fields.

The same situation is when i try install today versions of ispconfig on fresh D11.5.

There is no issue in ISPConfig on Debian 10.5 or your setup, so postfix is working fine. There is a known Webmin bug, Webmin cannot parse complex postfix files correctly. See the bug report here: https://sourceforge.net/p/webadmin/bugs/5402/

Is there any consideration regarding this guide if I've followed the "How To Use Multiple PHP Versions..." method on my ISPConfig server?? Currently I'm running an up to date Debian Buster  OS with PHP 56., 7.0, 7.1, 7.2, 7.3 and 7.4 versions installed. Thanks in advance

Thanks for this helpful howto. 

I have some minor suggestions. 

1.) Check available disk space before updating your system (reason: might require additional disk space during and after the update)

2.) Use the "screen" command when connected via SSH (reason: you can reconnect to a disconnected session)

3.) Wait for the changes to be applied in ISPConfig (wait for the red circle) after updating the paths of the default PHP version (reason: dunno what will happen when you proceed without waiting - this is just based on my gut feeling).

When is the expected update ISPConfig Server from Debian 11 to Debian 12?

Hello, some time ago I updated with the instructions "Update the ISPConfig Perfect Server from Debian 10 to Debian 11" to be able to use the latest version of WordPress, everything was ok until today when I saw that Let's Encrypt did not update the certificates of the 3 hosted pages, I tried to renew it manually and it gives the following error, do you have any idea how to fix it? Thank you very much Cesar

root@host:~# certbot -n renewTraceback (most recent call last):  File "/usr/bin/certbot", line 11, in <module>    load_entry_point('certbot==0.31.0', 'console_scripts', 'certbot')()  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in load_entry_point    return get_distribution(dist).load_entry_point(group, name)  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in load_entry_point    return ep.load()  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load    return self.resolve()  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in resolve    module = __import__(self.module_name, fromlist=['__name__'], level=0)  File "/usr/lib/python3/dist-packages/certbot/main.py", line 18, in <module>    from certbot import account  File "/usr/lib/python3/dist-packages/certbot/account.py", line 21, in <module>    from certbot import constants  File "/usr/lib/python3/dist-packages/certbot/constants.py", line 53, in <module>    tls_sni_01_port=challenges.TLSSNI01Response.PORT,AttributeError: module 'acme.challenges' has no attribute 'TLSSNI01Response'