• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Changing Main IP Adresse - Ineffective after restart

p0se

Basic Pleskian
Server operating system version
Ubuntu 22.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.47
Hello

I have added an IP address in the Plesk web interface.
This has changed the primary IP address of the server.

To fix this I made the following change

I set the old UP to main='true' and the new IP to main='false'.
The change took effect directly in the web interface. The old IP was displayed again as the primary IP.

After restarting the server, the new IP address is used as primary again.
Via IP a I now see that even after changes via the database, the old IP is listed as secondary.
Code:
    inet 45.67.139.NEW/24 brd 45.67.139.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 45.67.139.OLD/24 brd 45.67.139.255 scope global secondary eth0

How can I give the new IP the secondary status?
 
If I look into the file /etct/netplan/10-plesk.yml, there is also only one entry for the new IP.
Code:
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      addresses:
        - 2a0e:97c0:3e2:1b5::/64
        - 45.67.139.new/24
 
Back
Top