• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Failed to update the IP address" when repairing PHP-FPM configuration for all domains

CSKLDE

New Pleskian
Server operating system version
Debian Buster
Plesk version and microupdate number
18.0.56 Update #2
Hello all,

I'm encountering an issue when trying to repair the PHP-FPM configuration for all domains on my Plesk server. Here’s the command and output:
plesk repair web -php-fpm-configuration

Checking for obsolete PHP-FPM configuration files ................... [OK]

Checking php-fpm configuration

Repair php-fpm configuration for all domains? [Y/n] y
Repairing php-fpm configuration for all domains ................. [FAILED]
- Error: Failed to update the IP address. Addon domains cannot be assigned an IP address not assigned to the main domain of the subscription.
The repair process fails with the error:
"Failed to update the IP address. Addon domains cannot be assigned an IP address not assigned to the main domain of the subscription."
I use one IPv4 and one IPv6 for all domains.
 
@CSKLDE, most likely a database inconsistency persists, which results in a conflict. Please enable Plesk's debug mode and then run:

/usr/local/psa/bin/php_settings -u

to determine which domains are causing the issue. What you can try is to disable IPv6 for the corresponding domains and then re-enable it.
 
I've had a similar issue like that before, if you have docker containers running and the container isn't running any more you might have a left over IP address that the panel is seeing which is a simple fix of just removing it from within the settings (Tools & Settings > Tools & Resources > IP Addresses find the IP address that your old container was using and select it then hit remove)
 
I think plesk has some serious issues as we speak. The software stack is not compatible often. If you use the preinstalled things its all fine but if you require manual adjustments then it crashes instantly as hard as it can. Plesk can be only used for small projects, I am forcedt to use php8.1 and thats when things get ugly. Plesk simply cant handle this at all.
 
Back
Top