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

second IP blocked after reboot

T

tabita

Guest
After a reboot of my SuSE 9.1 - plesk 7.5.3 server, the second IP that it serves on eth0:1 is disabled. I found that SuSE's Plesk creates the file /etc/sysconfig/ifcfg-eth-id-XX:XX:XX:XX... which indeed contains the secondary (, ternary, ...) IPs, as it should. But why do those IPs not reappear after a reboot, and I have to explicitly switch them on in the PLESK interface?

Thanks,


Patrick
 
You must log in or register to reply here.

Similar threads

bigbear67
Question Network routing issue after update (loss of default route source IP / DNS failure on Ubuntu 24.04)
Replies
0
Views
1K
bigbear67
bigbear67
Phantasia
Issue Persistent iptables DROP Rule for Docker Container IP 172.17.0.2
Replies
7
Views
7K
Phantasia
Phantasia
T
Issue Unbanning some IP addresses causes the server to be unresponsive
Replies
4
Views
5K
TurabG
T
M
Issue Upgrade Debian 11.9 to 12 fails
Replies
0
Views
2K
MartinT
M
pr0tax
Issue Docker + Varnish - Reboot Mystery
Replies
1
Views
3K
mow
M
Back
Top