# Virtualmin Crashed

**URL:** <https://forum.virtualmin.com/t/virtualmin-crashed/137923>\
**Category:** Help! (Home for newbies)\
**Created:** [September 3, 2026, 9:38pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923 "2026-09-03T21:38:37Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![GeoffatMM](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/geoffatmm/32/533_2.png) [@GeoffatMM](https://forum.virtualmin.com/u/GeoffatMM)\
**Post date:** [September 8, 2026, 2:19pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/21 "2026-09-08T14:19:24Z")

</div>

> [@Randomz](#):
>
> How about build a fresh server

I am already on my fourth rebuild!

> [@jimr1](#):
>
> Are you using firewalld for firewall management ?

No Jim, Virtualmin no. longer installs firewalld as the default.

Joe/Ilia

Before I go and blast Ionos can you read this and let me know if there is any reason why it should happen from the Virtualmin side?

* * *

I have just (once again) deleted the server and rebuilt it using ubuntu 26.04 (no Docker).

I immediately rebooted and it was fine so the server itself appears not to be the problem.

I then did a clean install of virtualmin which pulled in package updates automatically. I did the post install wizard accepting the default values, did not add any more DNS servers and simply changed the email address and database password. I then checked the configuration and it was all OK. Virtualmin was flagging up a further 6 packages for renewal but I ignored them.

I then rebooted and it collapsed once again. It stuck on journal services which is immediately before it usually gives the logon. So something in the Virtualmin installation is creating an issue with the Ionos settings (init-cloud?).

I am happy to ask them to look into it but I just want to make sure we are confident it is not a possible issue with Virtualmin, especially as 26.04 is still registered as a class B (approved) installation.

Are there any other staging tests I can try? Can I force virtualmin to install without upgrading packages to see if it is one of those causing the issue?

Let me know if you are aware of anything, meanwhile I will gently bring it to the attention of the Ionos technical team.

Geoff

---

<div class="post-metadata">

**Author:** ![GeoffatMM](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/geoffatmm/32/533_2.png) [@GeoffatMM](https://forum.virtualmin.com/u/GeoffatMM)\
**Post date:** [September 8, 2026, 4:12pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/22 "2026-09-08T16:12:42Z")

</div>

Right,

Reinstalled 26.04 bare. Rebooted OK.  
Installed virtualmin using the -x flag to prevent upgrades or updates (which it skipped). Did the configuration wizard as before. Rebooted and it froze. So even the bare 26.04 is clashing with the Ionos setup.

Is no one else experiencing this issue?

The simple solution would be to revert to 24.04 LTS but although some of the install scripts show 26.04 as a class B at least one of the scripts I have used accepted it as a class A OS so it needs to be made to work.

I will now contact Ionos to ask them to look into it.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [September 8, 2026, 4:22pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/23 "2026-09-08T16:22:52Z")

</div>

> [@GeoffatMM](#):
>
> I have rebuilt the server. Upgraded all packages. Restored two virtual servers and nothing else.

Did you reboot after “upgraded all packages”? I don’t _think_ there’s anything in Virtualmin that can prevent booting. (Though it’s possible we install a package that conflicts with something the Ionos automation requires. We were surprised by the cloud-init vs. firewalld conflict, for example, and I remain annoyed that Debian/Ubuntu decided that was a reasonable packaging decision.)

Package updates remain the most likely culprit.

But, as Randomz notes, you need to be rebooting between each step to figure out when it actually fails so you can narrow it down. If the system won’t boot after you do all the steps to get it into service, then literally everything you do needs to be focused on narrowing the possible cause of that failure, and doing one isolated step at a time is the way to do that. If you see the failure after the package updates, you then narrow the list of packages to update to try to figure out _which_ package is a problem; cut it in half, update one half, test, then update the other half. And, so on.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [September 8, 2026, 4:24pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/24 "2026-09-08T16:24:45Z")

</div>

> [@GeoffatMM](#):
>
> Is no one else experiencing this issue?

No one else has reported a similar issue, but also not many people are using 26.04, as it is early.

If there is a problem, it seems most likely something conflicting with the cloud-init config or whatever automation Ionos uses for network configuration.

---

<div class="post-metadata">

**Author:** ![GeoffatMM](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/geoffatmm/32/533_2.png) [@GeoffatMM](https://forum.virtualmin.com/u/GeoffatMM)\
**Post date:** [September 8, 2026, 4:28pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/25 "2026-09-08T16:28:31Z")

</div>

Hi Joe,

I have rebooted at every step which is why I know that the base installation of the server (Ubuntu) is fine and it is only when I load Virtualmin (without any packages upgraded) that the problem occurs. I have tried to be forensic in finding the issue. I did intend to add the packages one at a time (there were 25 listed) to see if I could find the problem package but as it crashed with no package updates there was no need to.

I have just spoken with Ionos and the Ubuntu image is one that they have tweaked so it is possible they have tweaked something that clashes with Virtualmin. They also told me that my DVD drive has an option to load Ubuntu from the original iso file so that is my next task.

I will get back to you tomorrow.

---

<div class="post-metadata">

**Author:** ![pixel\_paul](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/pixel_paul/32/5262_2.png) [@pixel\_paul](https://forum.virtualmin.com/u/pixel_paul)\
**Post date:** [September 8, 2026, 4:30pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/26 "2026-09-08T16:30:12Z")

</div>

if you get another crash, try and post the `journalctl -b` log

---

<div class="post-metadata">

**Author:** ![jimdunn](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jimdunn/32/3487_2.png) [@jimdunn](https://forum.virtualmin.com/u/jimdunn)\
**Post date:** [September 9, 2026, 12:37am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/27 "2026-09-09T00:37:35Z")

</div>

It sounds like you’ve become an expert at re-imaging, so maybe try to re-image with the latest Debian, restore backups, see what happens??

---

<div class="post-metadata">

**Author:** ![Randomz](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Randomz](https://forum.virtualmin.com/u/Randomz)\
**Post date:** [September 9, 2026, 2:01am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/28 "2026-09-09T02:01:26Z")

</div>

Disclaimer: I know almost zilch about Ubuntu, but curiosity got me.

I created a new VPS on different provider (Binary Lane) using Ubuntu 26.04.

Apt upgrade, reboot, all OK.

Install Virtualmin, reboot, failed.

This pretty much confirms that it is between Ubuntu 26.04.1 and Virtualmin current, not the VPS provider - unless they use the same image.

---

<div class="post-metadata">

**Author:** ![Randomz](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Randomz](https://forum.virtualmin.com/u/Randomz)\
**Post date:** [September 9, 2026, 2:28am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/29 "2026-09-09T02:28:55Z")

</div>

I just repeated this but without apt-upgrade first.

Same result, won’t boot.

Repeated this with --type mini, same result - won’t boot.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [September 9, 2026, 2:36am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/30 "2026-09-09T02:36:25Z")

</div>

Can you look at the virtualmin install log and apt and dpkg logs before you reboot to see what package(s) were removed (if any) while installing Virtualmin?

In the past, the conflict with firewalld baked into cloud-init on Debian and Ubuntu was the cause of trouble (led to network not getting configured, because installing firewalld removed cloud-init, and if network was configured by cloud-init, then you wouldn’t have network after a reboot). I assume there must be something similar happening here, but I don’t have any guesses about what.

---

<div class="post-metadata">

**Author:** ![Randomz](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Randomz](https://forum.virtualmin.com/u/Randomz)\
**Post date:** [September 9, 2026, 3:19am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/31 "2026-09-09T03:19:33Z")

</div>

I deleted the VPS, don’t have time to get into diagnostics, was just happy to be able to confirm that it’s not Ionos VPS being the problem.

| (09 September 2026 to 09 September 2026 - 1.0 hours) | Server Operating System: Ubuntu 26.04 LTS (64bit) | Standard: 1 VCPU, 1GB RAM, 20GB Disk, 1000GB Transfer | $0.01 |
| --- | --- | --- | --- |

---

<div class="post-metadata">

**Author:** ![stefan1959](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/49beb7/32.png) [@stefan1959](https://forum.virtualmin.com/u/stefan1959)\
**Post date:** [September 9, 2026, 6:14am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/32 "2026-09-09T06:14:55Z")

</div>

I’m seeing this in console (using vultr), looks like a cloud-init conflict.  
OP seem to have a different output though

 ![image](https://cdn.forum.virtualmin.com/uploads/default/original/3X/1/5/15b4c5ecd2e222b745b13766b46212135796918c.png)

seems to be stuck there

found this bug report

> <https://github.com/canonical/cloud-init/issues/7052>
>
> \## Bug report
> 
> After upgrading an Ubuntu 26.04 (resolute) OpenStack VM from clou…d-init \`26.1-0ubuntu2\` to the SRU \`26.1-0ubuntu3~26.04.1\`, the \*\*first reboot never completes\*\*: the network stage blocks forever inside \`wait\_for\_network()\` on \`systemctl start systemd-networkd-wait-online.service\`. \`cloud-init-network.service\` ships \`TimeoutSec=0\`, and \`ssh.socket\`/\`docker.service\` are ordered after cloud-init, so the host ends up answering ICMP with \*\*zero listeners\*\* — effectively bricked (only provider-console/disk surgery recovers it). The hang reproduced deterministically on every boot attempt (4/4), including after a full stop/start of the VM.
> 
> The same image with \`26.1-0ubuntu2\` (fresh VM, same cloud, same datasource) executes the identical call in \*\*0.125 s\*\* — systemd starts networkd alongside wait-online and boot proceeds.
> 
> \## Environment
> 
> \- Ubuntu 26.04 LTS (resolute) cloud image, OpenStack provider (\`DMI: OpenStack Foundation OpenStack Nova\`), ConfigDrive (\`config-2\`) present, netplan renderer, single NIC (\`ens3\`, DHCP4)
> \- Broken boot: cloud-init \`26.1-0ubuntu3~26.04.1\`, systemd \`259.5-0ubuntu3.4\`, kernel \`7.0.0-30-generic\` (all three landed in one \`apt-get upgrade\`/\`dist-upgrade\` three days before the first reboot — so I cannot fully isolate cloud-init vs. systemd; the behavioral delta is in this code path)
> \- Working boot (for comparison): same image, cloud-init \`26.1-0ubuntu2\`, systemd \`259.5-0ubuntu3\`, kernel \`7.0.0-15-generic\`
> 
> \## Evidence (from the dead host's disk, post-mortem)
> 
> \`/var/log/cloud-init.log\` — these are the \*\*final lines\*\*; nothing follows for 28+ minutes until the VM was power-cycled:
> 
> \`\`\`
> main.py\[DEBUG\]: Will wait for network connectivity before continuing
> stages.py\[DEBUG\]: Using distro class \<class 'cloudinit.distros.ubuntu.Distro'\>
> activators.py\[DEBUG\]: Using selected activator: \<class 'cloudinit.net.activators.NetplanActivator'\> from priority: \['netplan', 'eni', 'network-manager', 'networkd'\]
> subp.py\[DEBUG\]: Running command \['systemctl', 'is-enabled', 'NetworkManager.service'\] with allowed return codes \[0\] (shell=False, capture=True)
> subp.py\[DEBUG\]: Running command \['systemctl', 'start', 'systemd-networkd-wait-online.service'\] with allowed return codes \[0\] (shell=False, capture=True)
> \`\`\`
> 
> Journal of the same boot: after \`Starting cloud-init-network.service - Cloud-init: Network Stage...\` at uptime ~6.5 s, \*\*systemd logs zero further job transitions\*\* for the rest of the boot (26+ min observed). \`systemd-networkd.service\` is never started in the main system (it ran only in the initrd, which got a DHCP lease fine and handed off). No \`Ordering cycle\`/\`Deleting job\` messages. The console shows only:
> 
> \`\`\`
> \[\*\*\* \] Job cloud-init-network.service/start running (9min 2s / no limit)
> \`\`\`
> 
> So the start job for \`systemd-networkd-wait-online.service\` (\`BindsTo=\`/\`After=systemd-networkd.service\`) is enqueued but never becomes runnable, networkd's pulled-in job never runs either, and since the caller \*is\* the unit the rest of boot is ordered behind (\`Before=sysinit.target\`), the wait can never be satisfied — a deadlock that systemd's transaction cycle-checker cannot see because the jobs arrive in a second transaction.
> 
> On the working \`26.1-0ubuntu2\` boot, the same sequence logs:
> 
> \`\`\`
> subp.py\[DEBUG\]: Running command \['systemctl', 'start', 'systemd-networkd-wait-online.service'\] with allowed return codes \[0\] (shell=False, capture=True)
> performance.py\[DEBUG\]: Running \['systemctl', 'start', 'systemd-networkd-wait-online.service'\] took 0.125 seconds
> \`\`\`
> 
> with the journal showing \`Starting systemd-networkd.service...\` immediately after \`Starting cloud-init-network.service...\`.
> 
> \## Impact
> 
> A routine SRU upgrade turned into an unbootable production host on its next (unrelated, provider-initiated) reboot. Because \`cloud-init-network.service\` has \`TimeoutSec=0\`, there is no bound at all: sshd never starts, and the machine cannot be recovered without out-of-band access.
> 
> \## Workarounds we validated
> 
> \- Drop-in on \`cloud-init-network.service\` with \`TimeoutStartSec=300\` — the stage's job fails at the bound and boot proceeds (sshd/docker come up; \`After=\` is satisfied by a finished job). This seems worth shipping as a belt-and-braces default given the blast radius of \`TimeoutSec=0\`.
> \- Booting with \`cloud-init=disabled\` also recovers the host.
> 
> \## Suggested angle
> 
> \`wait\_for\_network()\` issuing a \*\*blocking\*\* \`systemctl start\` from inside a unit that gates \`sysinit.target\` means any condition that keeps the started unit's job queued (rather than failing fast) converts to an infinite boot hang. Either the call needs its own timeout, or \`cloud-init-network.service\` should not ship \`TimeoutSec=0\`, or the wait should verify \`systemd-networkd.service\` is active/activatable before blocking on wait-online.
> 
> I no longer have the dead disk attached (provider reclaimed it), but I extracted full journals and logs for the broken and working boots before it went and can share more excerpts on request.

---

<div class="post-metadata">

**Author:** ![stefan1959](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/49beb7/32.png) [@stefan1959](https://forum.virtualmin.com/u/stefan1959)\
**Post date:** [September 9, 2026, 6:47am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/33 "2026-09-09T06:47:41Z")

</div>

After reinstall and install virtualmin I went and changed the time out to 60 seconds before any reboot. Then the system rebooted

 ![image](https://cdn.forum.virtualmin.com/uploads/default/original/3X/c/2/c258b9be6cdd9add58ac43a3384815a8d28ba35c.png)

console then reported this

 ![image](https://cdn.forum.virtualmin.com/uploads/default/original/3X/5/1/517cdbfad5c5809f8d719f4d64e530aadff01562.png)

But virtuamin seem to be working fine , any harm just disabling cloud-init services?

---

<div class="post-metadata">

**Author:** ![Randomz](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Randomz](https://forum.virtualmin.com/u/Randomz)\
**Post date:** [September 9, 2026, 7:12am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/34 "2026-09-09T07:12:27Z")

</div>

Not sure about Ubuntu, but I have done it on EL10 with my VPS provider in order to change from their IP to one of my own routed IP block.

First I create my own connection at  
/etc/NetworkManager/system-connections/eth0.nmconnection

Then these commands.

```auto
chmod 600 /etc/NetworkManager/system-connections/eth0.nmconnection

echo 'network: {config: disabled}' > /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

rm /etc/NetworkManager/system-connections/cloud-init-eth0.nmconnection

MAC=$(ip link show | grep -A1 "ens3\|eth0" | grep ether | awk '{print $2}')
echo "SUBSYSTEM==\"net\", ACTION==\"add\", ATTR{address}==\"$MAC\", NAME=\"eth0\"" > /etc/udev/rules.d/70-persistent-net.rules

```

This suits what I need it to do, I hope it can help you.

---

<div class="post-metadata">

**Author:** ![jimr1](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jimr1/32/14173_2.png) [@jimr1](https://forum.virtualmin.com/u/jimr1)\
**Post date:** [September 9, 2026, 7:51am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/35 "2026-09-09T07:51:35Z")

</div>

> [@Randomz](#):
>
> First I create my own connection at  
> /etc/NetworkManager/system-connections/eth0.nmconnection

Ubuntu 26.04 does not use NetworkManager, it uses NetPlan, which is totally different

---

<div class="post-metadata">

**Author:** ![Randomz](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/r/839c29/32.png) [@Randomz](https://forum.virtualmin.com/u/Randomz)\
**Post date:** [September 9, 2026, 8:17am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/36 "2026-09-09T08:17:59Z")

</div>

> [@jimr1](#):
>
> Ubuntu 26.04 does not use NetworkManager, it uses NetPlan, which is totally different

My point was to simply show that it is possible to disable cloud-init and the steps that I took with EL10.

Experienced Ubuntu enthusiasts could take inspiration and adapt for their own use.

---

<div class="post-metadata">

**Author:** ![jimr1](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jimr1/32/14173_2.png) [@jimr1](https://forum.virtualmin.com/u/jimr1)\
**Post date:** [September 9, 2026, 8:21am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/37 "2026-09-09T08:21:40Z")

</div>

> [@Joe](#):
>
> Can you look at the virtualmin install log and apt and dpkg logs before you reboot to see what package(s) were removed (if any) while installing Virtualmin?

Just did an install using virtualbox and there were no errors and the system rebooted fine after the virtualmin install. I do have the logs if you want them but I doubt they will help as I had a clean reboot. So maybe there is something odd with some providers deployments of Ubuntu 26.04.1

---

<div class="post-metadata">

**Author:** ![GeoffatMM](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/geoffatmm/32/533_2.png) [@GeoffatMM](https://forum.virtualmin.com/u/GeoffatMM)\
**Post date:** [September 9, 2026, 1:37pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/38 "2026-09-09T13:37:31Z")

</div>

Update on the original post.

I used the Ubuntu 26.04 iso via a virtual dvd drive provided by IONOS and installed Ubuntu. I allowed updates and upgrades, completed the installation and (after fiddling to get ssh server working properly) rebooted and it came back up.

Then did a full install of Virtualmin including setup wizard and updating some packages and rebooted and once again it came up fine.

Have not yet had time to reinstall the virtual servers but will do so tonight. I do not think they will cause a problem.

I have to conclude that the IONOS image clashes with Virtualmin for some reason but I do not know how to find out why. I will let IONOS know. At least any other IONOS customers will be able view this post to find a solution if they also get stuck.

I will confirm virtual servers go back OK.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [September 9, 2026, 6:10pm UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/39 "2026-09-09T18:10:52Z")

</div>

> [@stefan1959](#):
>
> any harm just disabling cloud-init services?

If your host is using it to configure network (as is pretty common), yes, there would be notable harm (you wouldn’t have network).

I am having a hard time coming up with anything we could be doing that would cause cloud-init to freak out. We don’t mess around with the things it configures, unless the user explicitly tries to configure network or something (which people on VMs absolutely should never do, since that’s the business of the hosting provider, you have no control over network IPs, etc. in a VM hosting environment).

When we depended on firewalld, that led to cloud-init being removed during install due to packaging bullshit in Debian/Ubuntu. But, we dropped firewalld so that wouldn’t be an issue.

So, I dunno. I don’t know why cloud-init seems so bound and determined to break so readily.

---

<div class="post-metadata">

**Author:** ![Ilia](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/ilia/32/10185_2.png) [@Ilia](https://forum.virtualmin.com/u/Ilia)\
**Post date:** [September 10, 2026, 12:44am UTC](https://forum.virtualmin.com/t/virtualmin-crashed/137923/40 "2026-09-10T00:44:47Z")

</div>

Have you by any chance run `virtualmin-config-system -i Quotas` on the old system? A fresh Virtualmin installation also runs this automatically.

If Ubuntu’s quota module is missing, there is a step that installs extra `kernel-module` packages. That should be harmless, but a custom kernel or an error rebuilding the `initramfs` could be relevant.

Could you check for any kernel or `initramfs` errors from `/var/log/apt/term.log`?

[Previous page](https://forum.virtualmin.com/t/virtualmin-crashed/137923.md?page=1)

[Next page](https://forum.virtualmin.com/t/virtualmin-crashed/137923.md?page=3)
