• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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)
 
Back
Top