ok,
my vps provider is changing the primary IP IPV4 address for my server and i tried changing > Virtualmin > Addresses and Networking > Change IP Addresses > Change Real Address and simply inserting the new primary IP there.
but that doesn't seem to be the way. or is it and i missed something?
under > Webmin > Networking > Network Configuration > Network Interfaces, there is venet0:0 which has the old primary IP address and venet0:1 which is the new primary IP address.
i tried to change the ip address of venet:0 to the new primary IP address contained in venet0:1, but an error message of "Failed to save interface : The interface venet0:1 is already using this IP address"
how to i set the server to the new primary IP address? do i vi /etc/hosts and stick the new primary ip address there?
thx,
Comments
Submitted by oneearth on Sun, 01/29/2017 - 20:53 Comment #1
i did change /etc/hosts and am hoping for the best. i haven't rebooted yet.
the virtualmin re-check config still picks up the old primary ip address.
i had changed my domain registrar settings for the ns1.vpsserver.com to the new primary ip address.
now i can't access roundcube. :-( i guess i'm in a limbo state where i haven't quite changed the correct setting.
your assistance is appreciated.
Submitted by andreychek on Sun, 01/29/2017 - 22:05 Comment #2
Howdy -- is the goal to put the new IP in the venet0:0 interface?
Or are you okay keeping it in venet0:1, and you just need to update the various config files with the new IP?
Submitted by oneearth on Mon, 01/30/2017 - 03:23 Comment #3
The goal is that on Feb 1st when the VPS provider eliminates the old primary IP address that is associated with venet0, that I would have prepared for that and that all the websites and email are still accessible.
Right now, I can only access roundcube email by using the explicit new primary IP address /roundcube. I'd like to get back a configuration that would allow me to use the domain name/roundcube method.
After changing /etc/hosts to the new primary IP and changing the IP address at my domain registrar, I can access virtualmin using domainname:10000, so that's good.
Any suggestions are appreciated so that come Feb 1st, my VPS, websites and email access will be referencing the new primary IP address.
Submitted by andreychek on Mon, 01/30/2017 - 08:58 Comment #4
Sorry for the confusion, but just to verify --
What interface do you want your new IP address on?
Do you wish to keep it on venet0:1, or is the goal to move it to venet0:0?
Or doesn't that actually matter to you?
Submitted by oneearth on Mon, 01/30/2017 - 15:14 Comment #5
My preference is not to have any references to the old primary IP around.
Come Feb 1st/2nd when the old primary IP will not be pointing to the server, I don't know what's going to happen to those interfaces.
Would a sensible choice be to move the new primary IP from venet0:1 to venet0:0 and then deleting venet0:1?
If that sounds sensible ,then I'd like to know how to make that happen.
Submitted by oneearth on Mon, 01/30/2017 - 16:47 Comment #6
oh, roundcube can now be accessed using the domain name. i guess it was a matter of waiting until dns propagation completed.
all dig's on the websites show the new primary ip address being used. Also, > Virtualmin > Server Configuration > Change IP address shows the new primary ip address being used.
Re-checking configuration shows the old primary IP address on venet0:0
Using network interface venet0:0 for virtual IPs.
IPv6 addresses are available, using interface venet0:0.
Default IPv4 address for virtual servers is 104.255.229.120.
...
Default IP address is set to 104.255.229.120, which matches the detected external address.
what needs to be done to have venet0:0 setup with the new primary ip address?
Submitted by andreychek on Mon, 01/30/2017 - 17:31 Comment #7
It sounds like you may want to delete the venet0:1 interface that contains the new IP address, and then edit venet0:0 to use the new IP rather than the old one.
You can modify the network interfaces in Webmin -> Networking -> Network Interfaces.
That will only change the network interface itself, that doesn't affect any other config files.
After making that change, you'll then need to update your config files to use that new IP address.
To update your config files, you'd want to go Addresses and Networking -> Change IP Addresses, and there you can change references to the old IP address to the new one.
Once that's done, reboot your server. When it comes back online, the network interface should be using your new IP address, and the config files should all be using the new IP.
If you can, you may want to make a backup of your server before doing all this.
Submitted by oneearth on Mon, 01/30/2017 - 17:36 Comment #8
ok, thanks for the rundown of the steps. i will do that later tonight.
Submitted by oneearth on Sun, 02/05/2017 - 21:44 Comment #9
hmm, the VPS provider eliminated the old primary ip address and virtualmin was looking for venet0:0 which was no longer showing (only venet0:1 with the new primary ip address was showing). Re-check Config was looking for venet0:0, so i deleted venet0:1 and added venet0:0 again with the new ip address (or so i thought).
then did the change id process. Re-check config was still saying the venet0:0 was not set with a ipv4 address. when i checked the Network Interfaces, venet0:1 was showing. i deleted it and now have lost access to virtualmin and can't even ssh in with the new ip address.
i can use the vps provider's console and the system seems to be running although webmin/virtualmin is not accessible, nor are the websites.
if you happen to get this message soon, and have some time for some troubleshooting advice, that would be great. otherwise, i may have to just start from scratch again :-(
Submitted by oneearth on Sun, 02/05/2017 - 21:54 Comment #10
oh, all it needed was the reboot as you mentioned above in your instructions. whew! ifconfig shows venet0:0 with the new primary ip address and Re-check Config is happy.
Thanks for the instructions!
Submitted by andreychek on Mon, 02/06/2017 - 09:14 Comment #11
That's fantastic, glad to hear things are working for you!
Submitted by oneearth on Tue, 02/07/2017 - 21:46 Comment #12