Hi there,
I have recently tried (once again) to install Virtualmin on an Ubuntu 18.04 droplet on DigitalOcean, with the following settings:
I believe private networking and/ or IPv6 is causing issues.
Unlike in the previous months where installation would fail to complete at all, this time, Virtualmin installs successfully and I am able to set up my virtual servers just fine. The issue arises when I reboot the droplet. After a reboot, I can no longer SSH into my droplet or access Virtualmin via the web interface. I can only access my droplet through the DigitalOcean console.
I believe there is still some misconfiguration in the networking settings on Virtualmin/ Webmin's part which prevents my setup from working properly. Would appreciate if this could be fixed. Thank you!
Working - 50-cloud-init.yaml. In newer installs it might be called 10-cloud something.yaml, but will be in the same location like /etc/netplan or /etc/netplan/*config Before you reboot, be sure ip, gateway and dns is correctly formatted.
1. Find the name of your network interface with terminal command 'ip address'.
2. Use that interface in place of the eth0 if different.
3. The hierarchy and spacing is important. Dont use tab for spacing, use space bar only.
4. address needs the ending suffix for your ip block. Just one Ip that will be /32.
5. Note brackets on address but not on gateway.
6. Note name server line spacing has to be further right than the "nameserver heading".
7. Note IPv6 dns addresses need quotes , Ipv4 does not. Brackets around all dns line.
8. adding an ipv6 address to the ip address line uses same format as the dns line with the addition of /64 or whatever your subnet is. Like addresses: [x.x.x.x/32,"2606:4700:4700::1111/64"]
Run 'netplan apply' before rebooting. Will show errors and line number where it is. Once no errors after running netplan apply. You can safely reboot. I'd still be careful editing net config with webmin/virtualmin as it may not do it correctly. But when manually set, it works fine.
# This file is generated from information provided by# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [xxx.xxx.xxx.xxx/28]
gateway4: xxx.xxx.xxx.xxx
nameservers:
addresses: ["2606:4700:4700::1111","2606:4700:4700::1001",1.1.1.1,1.0.0.1]
Thanks for the workaround! I will try it later when I get home.
Still, it would be great if this bug could be fixed. Aside from this, it seems that Virtualmin is good to go for 18.04
I did some quick troubleshooting and it turns out the problem was there was an extra indentation on set-name by default.
Backspaced a few times and it works now. Seems like a really silly bug that would be simple to fix.
However, noticed a few more issues with the current Netplan implementation, chief of all it seems to have issues supporting IPV6. case in point, I try to create a virtual server with IPV6 and it fails.
Currently, what I do is to overwrite 50-cloud-init with the digitalocean version after installation. Everything works except I can no longer enable Bind DNS despite me adding 127.0.0.1 to the nameservers, if I use the - function to delineate each IP address. I have to bracketise everything and separate each IP address by comma, which can get unwieldy if I have too many ipv6 nameserver entries.
There is also another issue I encounter with Ubuntu 18.04 on DO: nginx doesn't restart automatically upon rebooting. So far I have relied on this workaround: https://www.virtualmin.com/node/58789
@trenzterra did you make it working?
Yes, I am able to get Virtualmin LEMP to work just fine now, with the following workaround applied:
nano /lib/systemd/system/nginx.serviceChangeAfter=network.targettoAfter=network-online.targetRunsystemctl disable nginx.servicefollowed bysystemctl enable nginx.serviceHi all
I got a workaround running for the issue to lose connection after reboot:
https://github.com/webmin/webmin/issues/1077?_pjax=%23js-repo-pjax-conta...
Tomorrow i add 2 additional IPs and report here too ;-).
Good luck ;-).
No need to revert to 16.04. I solved all of my issues with Virtualmin on 18.04 LTS in several different server setups and the solution was:
Fresh Install: 1. Install 18.04 2. Install Virtualmin 3. Configure netplan thru Webmin only: -Webmin-Networking-Network Configuration
Then Webmin will generate the proper readable netplan .yaml file it needs
Already Installed: 1. Revert netplan to default .yaml file from fresh install of 18.04 2. Follow step no. 3 above
Don't forget:
**Any futur changes you need in netplan, use webmin. Otherwise upon reboot netplan will be broken again (until virtualmin has fixed the issue)
@kkyuco I always did this via webmin without a success, could you please let us know step by step your way? Screen cast world be helpful.
Please advise
Pardon my inexperience here. I have never screen casted nor do I know how to properly post code or commands. Bare with me please. Assuming you had made a copy of your default .yaml file similar to this:
I simply reversed the copy and rebooted:
Reboot the systen:
Now all ports are working and iP is dhcp so I fired up Webmin and configured my static iP Virtualmin for some reason messes with iPs if they were configured before it's install and after a reboot
I suspect that Webmin with Virtualmin in 18.04 cannot read a proper netplan setup as per Ubuntu netplan page and doesn't play well with pre-configured static iPs
Note: I also tried to configure iP and iPs in netplan after install of Virtualmin. They worked, but after a reboot the same issues
For the future experience you can use a very easy solution at: https://screencast-o-matic.com/