Go to Virtualmin
select server
navigate to Server Configuration->Change IP Address
fill in the form
the response is
check back in Webmin->Networking->Network Configuration->Network Interfaces you see
and
from this webmin is aware of eth0 being up but not started at boot, however it is as everything works fine until you try to add a virtual interface. if you try to add a virtual interface via Webmin->Networking->Network Configuration->Network Interfaces and name it the name of whatever, in this case I used eth0:1
any ideas on how to fix ?
Status:
Active
Virtualmin version:
162
Webmin version:
1960
Comments
Submitted by JamieCameron on Wed, 10/21/2020 - 21:35 Comment #1
Looks like Virtualmin cannot find your boot-time network interface config.
Which Linux distro are you running there?
Ubuntu 20.04
Submitted by JamieCameron on Sat, 10/31/2020 - 19:27 Comment #3
Can you post the contents of the files in your
/etc/netplandirectory to this bug report?there are no files in
/etc/netplanSubmitted by JamieCameron on Sun, 11/01/2020 - 16:06 Comment #5
Does the directory exist at all?
If not, what does your /etc/network/interfaces file contain?
the directory is there but empty and the content of /etc/network/interfaces is
auto loiface lo inet loopback
auto eth0
iface eth0 inet static
address 37.122.211.130
netmask 255.255.252.0
gateway 37.122.211.254
dns-nameservers 46.32.224.29 46.32.224.30 46.32.224.31
dns-search vps-10.com
However Webmin sees it a bit differently the dns servers are not set to the above IP's but in fact to google's servers (8.8.8.8, 8.8.4.4) and no dns-search is set. As a foot note this machine is a vps .. & from what i can see it's in a kvm container
BIOS Information
Vendor: Seabios
Version: 0.5.1
Release Date: 01/01/2007
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
BIOS characteristics not supported
Targeted content distribution is supported
BIOS Revision: 1.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Red Hat
Product Name: KVM
Version: RHEL 6.6.0 PC
Serial Number: Not Specified
UUID: 63b906c5-7b0a-01e0-1cf6-fce701bc20b5
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Red Hat Enterprise Linux
I did try to save the network settings via Webmin which webmin accepted until I rebooted ... at this point the vps would not start and the only way out of this was to reprovision the server ... tried this twice same result.
Submitted by JamieCameron on Tue, 11/03/2020 - 22:31 Comment #7
Ok - the quick fix for this issue is to delete that empty /etc/netplan directory.
Ok did that what's next ? currently I can add a new IP address, which works, but I can not make it persistent if I add eth0 start at boot via webmin and reboot the network does not restart only way out of this is to reprovision the VPS and start from scratch (now on to the tenth attempt). I have another webmin managed server which I reprovisioned and only upgraded it to 18.04 which behaves normally and the netplan directory with .yaml files. Any reason for that ?
Submitted by JamieCameron on Sun, 11/08/2020 - 19:34 Comment #9
So when you re-provision a VPS, does it have the primary IP address listed in /etc/network/interfaces or a file /etc/netplan ?
netplan is always empty
/etc/network/interfacesis as you see it aboveDoes everything work as expected after deleting
/etc/netplandirectory?no I had to reprovision again .. I guess it's just the way it is
If you delete
/etc/netplandirectory (considering it's empty) before installing Virtualmin and Webmin - does it work?Does it have Webmin pre-installed?
What is the output of
/etc/network/interfacesand/etc/resolve.confbefore and after installing Virtualmin? Is/etc/resolv.confa symlink or a file?What exactly fails? Connection lost upon a reboot? Can you access your server using IP address instead?
Service Provider is webfussion/123-reg Plan is unmanaged VPS Webmin is not preinstalled Resolv.conf is a symlink to ../run/resolvconf/resolv.conf I have never viewed the files before installing webmin/vm so I have no idea what they contain unless I reprovision again. The vps runs correctly (boots up) unless I add an interface to start at boot then on reboot the vps appears (from the provider control panel) to be stuck in a boot loop, I am guessing the network interface is not coming up through mis configuration .. the only fix is to reprovision. As this is a production server I can only try these things occasionally as there is too much down time for the users
What is the output of
/etc/network/interfacesand/etc/resolve.conffiles?Is
/etc/netplandirectory exists? If you run commandnetplanin the console, what is the output?/etc/netplanhas been deleted the output from netplan is thus :-/etc/network/interfaces/etc/resolv.confI have restarted the server due to other webmin issues and lo and behold the network came up so I guess removing the netplan directory fixed the issue