• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

XMLRPC error message "Unable to get ip id by address from db" when adding domains

G

GrahamW

Guest
I'm getting the following response from the server:

<packet version="1.6.0.1">
<domain>
<add>
<result>
<status>error</status>
<errcode>1023</errcode>
<errtext>Unable to get ip id by address from db</errtext>
</result>
</add>
</domain>
</packet>

after attempting to add a new domain on an existing shared IP address on the server.
I have checked and confirmed that the IP address is valid, in the system, and it the same as is returned when I send a packet off to query for available IPs.

Any help on tracking down this issue would be helpful. Thanks.
 
Try to reread IPs on this Plesk server and make sure that this IP is really exists in client's IP pool.
 
I have reread the IPs, and confirmed they are correct and valid.
The user I am using to test the XMLRPC API is the admin user. How do i get this IP address included in the admin users IP pool?
 
I have refreshed the IPs, and confirmed the set are valid.
Current testing is using an administrative user for connection via the API.
Do the IP addresses need to be assigned to a pool for this user in order to correct this error message?
 
Back
Top