• 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.

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