This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
Sure, you can edit all the IPs for a Xen instance at Resources -> Network Interfaces. This can be done when it is offline, and the .cfg file will be updated too.
If the VPS cannot be pinged ( in this case ), or SSH has failed, then that menu isn't available. A VPS that has been shutdown, however does show the menu.
I moves a VPS from one server to another, but I think the IP didn't change properly, so now it's in a "Ping failed" state. So, I wanted to change the IP, but can't since the menu option isn't there.
I also noticed this for a VPS with "No SSH Access", so even though it is running, I can'tg change the IP either.
That is actually expected .. for Cloudmin to change the IP, it needs to be able to edit the network config files on the VPS. It can do this when it is down (by mounting the filesystem), or when it is fully up (by SSHing in), but not when it is running but un-pingable.
Ok, fair enough, but what about when it doesn't have SSH access? Why not be able to change the IP in the configuration file (/xen/vps.cfg) in that case still?
Would you really want to do that though? It seems like if the .cfg file had one IP but the guest's eth0 was using a different one, networking would be broken..
well, it's "broken" already :) So, with this, instead of having to shutdown, change IP, startup, why not make it one step simpler: change IP (regardless if it's non-pingable or not?) > Reboot ?
Sure, you can edit all the IPs for a Xen instance at Resources -> Network Interfaces. This can be done when it is offline, and the .cfg file will be updated too.
''
That option isn't available when the VPS is down, hence my question :)
Are you sure? It appears OK for me ..
I made a mistake in my original post though - it is at System Configuration -> Network Interfaces.
If it isn't appearing for you, which Linux distribution is the VPS running?
''
Ok, I see now.
If the VPS cannot be pinged ( in this case ), or SSH has failed, then that menu isn't available. A VPS that has been shutdown, however does show the menu.
I moves a VPS from one server to another, but I think the IP didn't change properly, so now it's in a "Ping failed" state. So, I wanted to change the IP, but can't since the menu option isn't there.
I also noticed this for a VPS with "No SSH Access", so even though it is running, I can'tg change the IP either.
After shutting down the VPS, the menu appears. So it seems like it's bug, whereby the menu isn't visible in all the different states.
That is actually expected .. for Cloudmin to change the IP, it needs to be able to edit the network config files on the VPS. It can do this when it is down (by mounting the filesystem), or when it is fully up (by SSHing in), but not when it is running but un-pingable.
''
Ok, fair enough, but what about when it doesn't have SSH access? Why not be able to change the IP in the configuration file (/xen/vps.cfg) in that case still?
Would you really want to do that though? It seems like if the .cfg file had one IP but the guest's eth0 was using a different one, networking would be broken..
''
well, it's "broken" already :) So, with this, instead of having to shutdown, change IP, startup, why not make it one step simpler: change IP (regardless if it's non-pingable or not?) > Reboot ?
Ok, I'll see what I can do here for a future release.
''