Issue IP address not found on interface(s) and broken binding for domains

[proflead]

Hello,

After rescale, vServer cannot open any websites on it.

The server work on Ubuntu 16.04.

When run comman via SSH plesk repair all –n see the following errors:
….
There are incorrect permissions on some items: /var/www/vhosts .... [ERROR]
….
Checking for nginx ULIMIT value
28 domains have been found on server. Problem with nginx default
limit for open files is possible
Please check nginx fails to start/reload on a Plesk server: Too many open files for
details ........................................................... [WARNING]
….
IP address not found on interface(s): 172.31.1.100 ................ [ERROR]

Broken binding for domain: worldcoffeebeans.com ................... [ERROR]

If I run the repair command but all websites open plesk default page even there is no index.html with this code in the domains folders.

Please help to solve the problem.

Thank you in advance.

 

[Flying-Hawk]

I've the same issue after IONOS migrated my cloud server, any solution on this issue?

I can't access my plesk login 8443 or website anymore, although I've set the right IP in port 8443.

Any help would be appreciated.

 

[Kaspar@Plesk]

@Flying-Hawk there is a support article which covers this issue and provides a possible solution:

https://support.plesk.com/hc/en-us/articles/12377434167447-Apache-default-page-is-shown-in-the-browser-instead-of-website-hosted-in-a-Plesk-server-Error-IP-address-not-found-on-interface

 

[Flying-Hawk]

@Flying-Hawk there is a support article which covers this issue and provides a possible solution:

https://support.plesk.com/hc/en-us/articles/12377434167447-Apache-default-page-is-shown-in-the-browser-instead-of-website-hosted-in-a-Plesk-server-Error-IP-address-not-found-on-interface

Thank you for the fast reply.

I already checked that page, but I can't access Plesk via the online interface, I can only use the terminal of IONOS to access it.

There I used the command: plesk bin ipmanage --reread

Unfortunately it didn't solve anything.

 

[Flying-Hawk]

This is what I get for "# plesk repair web -y":



This is how my IP is listed in Plesk:

 

[Kaspar@Plesk]

Does the IP address and network interface match with the output of ifconfig?

 

[Kaspar@Plesk]

Also I think you need to "re-map" the domains to the new IP address first. This will help probably help you:

https://support.plesk.com/hc/en-us/articles/12377887745687-How-to-change-the-IP-address-for-a-domain-in-Plesk

 

[Flying-Hawk]

Hi,

I unfortunately can't login outside the plesk shell, I've tried with putty, but it wont allow it, inside plesk I can't use "ifconfig".

I tried remapping the domains, and it tells me that the ip is already used.

I now got another public ip from IONOS, and tried to connect it to plesk with this tutorial:

How to add a new IP address to a Plesk server - Support Cases from Plesk Knowledge Base

How to add a new IP address to a Plesk server - Support Cases - Plesk Knowledge Base

www.plesk.com

But plesk gives me this:


It's getting frustrating, because I don't really know what I'm dealing with, I need to get access to my plesk because of the files I've there.

 

[Kaspar@Plesk]

That's probably because the network interface "eth0" does not exist on your server. From the output of plesk bin ipmanage -l it looks like the network interface on your server is named "ens192". However I don't think adding a new IP will solve your issue.

I recommend reaching out for assistance to either your provider or Plesk support. They can help you with direct access on your server.

To sign-in to Plesk support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[BuzzLightBurger]

I too recently had a small disaster with an IONOS cloud server.

Although the primary IPv4 address remained unmolested (as did my 2nd IPv4) address, following a reset at the new Data Center, the IPv6 address range updated on my IONOS account (it remained wrong for weeks after the migration which obviously didn't help).

After using the virtual KVM to access the server via the IONOS website, I was able to reconfigure /etc/network/interfaces with the networking information:
(which were later confirmed by their level 2 support to be correct)

your_public_ipv4/32 & your_public_ipv6/64
(DHCP seems to issue the wrong gateway address, using the previous cloud gateway IP [starting 10.] which is now wrong)

New Gateway Addresses = first_three_octets_of_your_public_ipv4_address_plus_.1 & fe80::1 for IPv6 IPs.

DNS Addresses: (/etc/systemd/resolved.conf)
DNS=212.227.123.16 2001:8d8:fe:53:72ec::1
FallBackDNS=212.227.123.17 2001:8d8:fe:53:72ec::2

You will probably find that Plesk then complains about addresses NOT present on interface (ens192) which requires you to use SQL to find the offending ID's of the old addresses and then replace all reference to that old IP_ID (or ID's) and replace them with the ID(s) used for the new IP addresses..

Plesk will probably just error trying to delete the old IP addresses as they will be linked to domains or mail services and no amount of fixing the issue using scripts will help.

[this task is actually easier than it sounds once you've regained access to Plesk's GUI]

Then Plesk will probably make a mess of the web config files after the ID(s) have been correctly assigned (if you save a domain's hosting setting for example), but that's a simple case of regenerating the configs thankfully. It happened once and then never repeasted itself.

The changes at IONOS also broke the IPv6 connectivity to the server (defunct addresses and an incorrect gateway), which of course broke Let's Encrypt SSL cert renewals as that service uses IPv6 to read the DNS txt record.

This too is resolved once you repair the IPs, removing the dead IPs from Plesk's DB and ensuring your new gateway IPs are set.

After IONOS broke my server, they pretty much only wanted me to migrate my sites to another server, I had other ideas and now everything is back online and error free..

It would be nice if they employed more people that understood the systems their servers operate, to expedite repairs, but hey ho.
I just love asking the same question over and over again and getting some unrelated/uneducated response back from them lol..

Good luck with it.