Servus
Basic Pleskian
Hi @ Plesk friends,
4 weeks ago I migrated Plesk Obsidian 18.0.33 with Ubuntu 20.04.2 on Ionos dedicated server and Cloud Panel.
Important is the very last point. In real it is a Cloud server (BUT) with dedicated fixed environment, it's a dedicated server in Cloud administration.
To realize own name server (ns1.domain.com) I have 2 additional IPv4 and the main IPv4, all this name server is working fine. I also added 3 IPv6 to network/interfaces.
This nameserver environment I use without problems since years.
To add the IPv4 I used the help+support articles by Ionos for dedicated server. But the network failed (ifup: failed to bring up eth0:0)
eth0 is the main IPv4
eth0:0 is the 1st additional IPv4
eth0:1 is the 2nd additional IPv4
Interesting is it works. All IPs v4 and v6 are accessible in Plesk and used for webhosting, but with a failed network ! ! ! ! !
This is the amazing Ionos way, network service is down, but IPs are working.
The amazing Plesk way is: You can add IPs over Plesk Panel, without adding them in Ubuntu, they are working. First I always add the IPs in Plesk Panel, then I realize, oh damn, I have something forgotten, adding them in OS first. Since Ubuntu 14 it's always the same. But it works...
Only one point is not working, in the actual environment of the last weeks!
Every 12 hours the access of IPs and so for the whole server including SSH is lost. I can only restart the server over Cloud Panel and then it works again for the next 12 hours. In logs I only get the messages that there are resolving problems. I opened a support ticket in Ionos without results.
Then I used the support article for CLOUD SERVER. And now network is running successfully.
After reload all IP addresses in PLESK Panel the main server IPv4 , which is always printed in bold letters is not bold, but the first additional IPv4 is shown now in bold letters.
That's crazy, isn't it? And:
The problem with loosing access every 12 hours still exists.
On my old server with Ubuntu 18.04 I used a network/interfaces configuration which was in no support article, with configuring iface eth0 inet dhcp what you normally shouldn't use together in a configuration with eth0:0. Don't know to take the risk and add it to /interfaces/ once again? .
Actual configuration:
4 weeks ago I migrated Plesk Obsidian 18.0.33 with Ubuntu 20.04.2 on Ionos dedicated server and Cloud Panel.
Important is the very last point. In real it is a Cloud server (BUT) with dedicated fixed environment, it's a dedicated server in Cloud administration.
To realize own name server (ns1.domain.com) I have 2 additional IPv4 and the main IPv4, all this name server is working fine. I also added 3 IPv6 to network/interfaces.
This nameserver environment I use without problems since years.
To add the IPv4 I used the help+support articles by Ionos for dedicated server. But the network failed (ifup: failed to bring up eth0:0)
eth0 is the main IPv4
eth0:0 is the 1st additional IPv4
eth0:1 is the 2nd additional IPv4
Interesting is it works. All IPs v4 and v6 are accessible in Plesk and used for webhosting, but with a failed network ! ! ! ! !
This is the amazing Ionos way, network service is down, but IPs are working.
The amazing Plesk way is: You can add IPs over Plesk Panel, without adding them in Ubuntu, they are working. First I always add the IPs in Plesk Panel, then I realize, oh damn, I have something forgotten, adding them in OS first. Since Ubuntu 14 it's always the same. But it works...
Only one point is not working, in the actual environment of the last weeks!
Every 12 hours the access of IPs and so for the whole server including SSH is lost. I can only restart the server over Cloud Panel and then it works again for the next 12 hours. In logs I only get the messages that there are resolving problems. I opened a support ticket in Ionos without results.
Then I used the support article for CLOUD SERVER. And now network is running successfully.
After reload all IP addresses in PLESK Panel the main server IPv4 , which is always printed in bold letters is not bold, but the first additional IPv4 is shown now in bold letters.
That's crazy, isn't it? And:
The problem with loosing access every 12 hours still exists.
On my old server with Ubuntu 18.04 I used a network/interfaces configuration which was in no support article, with configuring iface eth0 inet dhcp what you normally shouldn't use together in a configuration with eth0:0. Don't know to take the risk and add it to /interfaces/ once again? .
Actual configuration:
Attachments
Last edited: