Proxmox Hanging After NS8 Core Update on Rocky VM

Support
1

I have two different NS8 installs on Proxmox VMs. Both were working flawlessly. One is a Debian 12 OS and the other was the Rocky VM. Now neither are working after doing the latest NS8 Core Update from the UI. The Debian 12 boots to shell, but I can no longer access the UI from a browser. The Rocky hangs in my Proxmox console at the Probing EDD prompt. Pressing ‘e’ on boot returns

2026-08-18 NS8 Rocky on Proxmox Hanging
2026-08-18 NS8 Rocky on Proxmox Hanging799×567 15.1 KB

Anyone else have this issue? I haven’t changed anything in the VM hardware of either machine - simply did the core updates from the NS8 UI of each. I knew it would be a gamble with the Debian 12, but the Rocky is supported by the NS team, right? Shouldn’t break if you’re putting out the updates. I haven’t altered any scripts and the install is fairly new. Again, it was working. I tried changing some hardware settings in PM, i.e., CPU and display types, to no avail.

2

Thanks for the report. These look like two separate symptoms on two separate installs, so let’s split them.

Rocky VM (stuck at boot)

  • Let it sit at Probing EDD for a few minutes without touching anything — on some Proxmox configs this stage is just slow, not stuck.
  • If it’s still stuck after that, reboot, press e on the boot entry, and paste the full text shown (not a partial screenshot).
  • What exact Rocky Linux release is this (check in Proxmox VM hardware notes, or cat /etc/rocky-release if you can get a rescue/live shell)?
  • In the Proxmox VM’s Hardware/Options tab: BIOS type (SeaBIOS or OVMF) and Machine type (i440fx or q35)?
  • Which NS8 version was this cluster on before the Core Update, and which version did the update target? (Settings → Software Center → update history)
  • Besides the NS8 Core Update from the UI, did you also run a system package update on this VM (e.g. dnf update), before or after? The NS8 Core Update itself only pulls Podman images and runs application-level scripts, it doesn’t touch the kernel, initramfs or GRUB — so if the boot is affected, it would help to know if something else touched the OS packages around the same time.

Debian 12 VM (boots to shell, UI unreachable)

Since you have shell access, please run these and paste the output (remove any password, token, certificate, public IP, domain name or email address first):

journalctl -e --no-pager -n 200

Then check the core Traefik module:

runagent -m traefik1
systemctl --user status
exit

And same question as above: which NS8 version before/after the update, and did you run any OS package update alongside the NS8 Core Update?

This will tell us whether it’s a bootloader/kernel issue unrelated to NS8 on the Rocky side, and a module-startup issue on the Debian side.

3

I have done this, repeatedly, for good lengths of time…after any hardware changes I try it also.

paste the full text

Seen word wrapped in pic above.

BIOS type (SeaBIOS or OVMF) and Machine type (i440fx or q35)

SeaBIOS and i440fx, but I’ve tried alternates, to no avail.

What exact Rocky Linux release

On boot, prior to Grub, I can see the choice is Rocky Linux 9.7, by default.

Which NS8 version

Can’t get into the UI because the machine won’t boot past the image I pasted in my original post.

did you also run a system package update on this VM (e.g. dnf update)

No. It’s a fairly new install I didn’t spend much time on, until recently. Recently being, since I can’t access my NS8 UI on the Debian 12 VM.

4

Not sure if this is relevant, but it’s a hang at the same point:

5

Yeah, I looked through that one before I even posted my thread. As I stated, it was a working Rocky with NS8 VM, i.e., until I did the NS8 core update.