These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for After update Webmin thinks the IP address has changed on the new forum.
Installed webmin update via yum from the Webmin repo
Now it produces
Warning! Your system's primary IP address appears to have changed from xxx.xxx.xxx.xxx.xxx to 127.0.0.1. Virtual servers using the old address may be unreachable or serve the wrong web content.
I have changed nothing = what is causing this and how to address it ??
I have searched for this common occurrence and most say letting webmin make changes trashes the system which is working
I do not want Webmin to change or adjust anything - I just to turn the message off
Centos 7 fully up to date, 4 core OpenVZ VPS with local nameserver, recently upgraded to php 7.3.5, php-fpm via unix sockets
The message is WRONG
I discovered this in network configuration - the spoaces are needed because this site otherwise puts it all on one line
Name Type IPv4 address Netmask IPv6 address Active
lo Loopback 127.0.0.1 255.0.0.0 Yes
venet0 OpenVZ 127.0.0.1 255.255.255.255 From IPv6 discovery Yes
venet0:0 OpenVZ (Virtualmin) xxx.xxx.xxx.xxx 255.255.255.255 Yes
venet0:1 OpenVZ (Virtualmin) xxx.xxx.xxx.yyy 255.255.255.255 Yes
This was from the interfaces "Activate at Boot" TAB - it looks correct
This below is from the "Active Now" TAB
lo Loopback No address configured None ::1 Up
venet0 OpenVZ No address configured None Up
venet0:0 OpenVZ (Virtual) 127.0.0.1 255.255.255.255 Up
venet0:1 OpenVZ (Virtualmin) xxx.xxx.xxx.yyy 255.255.255.255 Up
I went back to the "change IP" page the error message links to - and changed the IP to the old original IP - and unchecked update DNS and changed it to "virtual servers only selected" and left NONE highlighted so Webmin should see there would be no reason to edit the etc/httpd/httpd.conf file "in theory" to mess with or reason to mess with the etc/named.conf file
The error is gone now however the "Active Now" TAB remains the same - which should be WRONG and possibly a bug
Centos7