WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended pro

Dear all, I get following error upon trying to update ISPConfig 3 on my server. I find absolutely nothing about it online except one pull request on someone's gitmemory. Please help!

Operating System: Ubuntu 20.04.3 LTS (Focal Fossa)

This application will update ISPConfig 3 on your server.

Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]:

Creating backup of "/usr/local/ispconfig" directory...
Creating backup of "/etc" directory...
Checking ISPConfig database .. WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.
OK
WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.
Starting incremental database update.
Loading SQL patch file: /tmp/ispconfig3_install/install/sql/incremental/upd_dev_collection.sql
Reconfigure Permissions in master database? (yes,no) [no]:

 

I think it was the cause once of a corrupted one of my apache site files; it said something like <xxxthisshouldbehere WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.> which caused the whole thing to break of course. It just amazes me how seemingly almost no one on the Internet has had the same problem.

 

FYI: this happened to me after upgrading (by mistake) from MariaDB 10.5 to 10.9 (which looks like to just work perfectly fine with ISPConfig so far).

Anyway, you need to make sure to add
bind-address = ::
to your my.cnf in /etc/mysql/my.cnf

Afterwards, Multiserver setup worked again and the error has been gone.

 

Just got this during update on a fresh migration, ispconfig running on 22.04 server with no ipv6.
Do we have any news on how to fix this error message?