I think it was yesterday evening that the upgrade to Usermin finally dropped for my Virtualmin managed server. I installed that, then updated the theme and went to bed. My Ubuntu 16.04 server was fully updated at that point. This morning I had a tree fall in a neighbors yard onto the main power lines, so before the APC-UPS powered down my server automatically, I went to the terminal at the server and ran sudo shutdown now. The power was restored about 3 hours ago and after restarting my server I cant go to https://myhostname.mydomainname.tld:10000 and get a page. I thought since Apache2 looks like its running, the sites managed should launch, but they don't seem to go.
My Linux command line skills are dated so I don't know what to do to solve this. I did do this though hoping it would help diagnose the problem:
myusername@myhostname:~$ service --status-all
[ + ] acpid
[ + ] apache-htcacheclean
[ + ] apache2
[ + ] apcupsd
[ + ] apparmor
[ + ] apport
[ + ] atd
[ + ] bind9
[ - ] bootmisc.sh
[ - ] cgroupfs-mount
[ - ] checkfs.sh
[ - ] checkroot-bootclean.sh
[ - ] checkroot.sh
[ + ] clamav-daemon
[ + ] clamav-freshclam
[ + ] console-setup
[ + ] cron
[ - ] cryptdisks
[ - ] cryptdisks-early
[ + ] dbus
[ + ] docker
[ + ] dovecot
[ - ] ebtables
[ + ] fail2ban
[ + ] firewalld
[ + ] grub-common
[ - ] hostname.sh
[ - ] hwclock.sh
[ + ] irqbalance
[ + ] iscsid
[ ? ] jailkit
[ + ] keyboard-setup
[ - ] killprocs
[ + ] kmod
[ ? ] lookup-domain
[ - ] lvm2
[ + ] lvm2-lvmetad
[ + ] lvm2-lvmpolld
[ + ] lxcfs
[ - ] lxd
[ + ] mdadm
[ - ] mdadm-waitidle
[ + ] memcached
[ + ] memcachedb
[ + ] milter-greylist
[ - ] mountall-bootclean.sh
[ - ] mountall.sh
[ - ] mountdevsubfs.sh
[ - ] mountkernfs.sh
[ - ] mountnfs-bootclean.sh
[ - ] mountnfs.sh
[ + ] mysql
[ + ] networking
[ + ] ondemand
[ + ] open-iscsi
[ - ] open-vm-tools
[ + ] php7.0-fpm
[ - ] plymouth
[ - ] plymouth-log
[ + ] postfix
[ + ] postgresql
[ + ] postgrey
[ + ] procps
[ + ] proftpd
[ + ] quota
[ - ] quotarpc
[ + ] rc.local
[ + ] redis-server
[ + ] resolvconf
[ - ] rsync
[ + ] rsyslog
[ + ] saslauthd
[ - ] screen-cleanup
[ - ] sendsigs
[ + ] spamassassin
[ + ] ssh
[ + ] sysstat
[ + ] udev
[ + ] ufw
[ - ] umountfs
[ - ] umountnfs.sh
[ - ] umountroot
[ + ] unattended-upgrades
[ - ] ups-monitor
[ + ] urandom
[ - ] usermin
[ - ] uuidd
[ - ] webmin
[ - ] x11-common
myusername@hostname:~$
Comments
Not sure how significant this is, but the power outages were severe enough to cause a FiOS disruption such that my dynamic IP address changed. I updated it on the domain registrar that I use, but don't know how to fix it in places that Webmin and assorted programs would need it changed.
Submitted by andreychek on Wed, 04/04/2018 - 17:05 Comment #2
Howdy -- yeah having a dynamic IP address can cause some issues, we'd definitely recommend using a static IP.
However, let's start here -- what happens when trying to access Webmin or any of your websites? What error do you see?
What if you access Webmin using an IP address rather than a domain name, does it work in that case?
Are you able to SSH to your server and access it that way?
And where is DNS being hosted for your domains, is that hosted on your Virtualmin server, or on a third party service such as your domain name registrar?
Shit. I guess that dynamic IP address was THE big thing.
After the Time To Live at my domain registrar flipped over my Virtualmin started again.
So before this is closed, how do I maintain the records managed by Virtualmin to update that new IP address? A link to an old issue will make me happy.
Replying to @andreychek #2 I was getting the default "Problem Loading Page" from the browser for everything. I didn't get to try it as an IP address before it started working again, and at no time did I have trouble going in via SSH.
I'm using (no judgment's please) domains.google.com for my sites right now.
Submitted by andreychek on Wed, 04/04/2018 - 22:55 Comment #5
It can be very difficult to use a setup where your server's IP is dynamic, as all your DNS records would be incorrect anytime that IP changes.
In that regard, we always recommend a static IP -- using a dynamic IP can lead to a lot of problems, and a difficult setup to manage/maintain.
However, for those who really wish to go down that route -- you could look into the option in Addresses and Networking -> Dynamic IP Update.
I'm not too familiar with it... it says that it attempts to update the IP address of the DNS records, which implies that they need to be hosted on your server.
What I don't understand with that is that for them to be hosted on your server, that means it would also need to be configured as a nameserver at your registrar -- and that IP can't be dynamically updated. So honestly I don't even know how that'd work, but you're welcome to take a look and see how that works for you.
If you really must use a dynamic IP, I'd probably instead suggest looking into a dynamic IP service which can manage all the DNS records for you.