Boot stuck on "A start job is running for Network initialization (XXm / no limit)"

signalcodec

New Member
Apr 13, 2020
7
0
1
32
Exactly as the title suggests; after a reboot this morning proxmox will not complete its boot, timer is just ticking with no end in sight. And I can't get into proxmox to find out an underlying issue.

Help!
 
If the the task does not stop - boot with a live-CD and check the contents of your /etc/network/interfaces
else try looking into the system's journal for hints what caused the delay (journalctl -b)

I hope this helps!
 
I had the same problem when I was trying to install Proxmox Backup Server on top of Debian 11. Commenting auto IPv6 config out in /etc/network/interfaces fixed the issue:
# iface enp0s25 inet6 auto

Strange thing is the interface (enp0s25) gets correct auto IPv6 configuration even with the line above commented out.
 
Last edited:
I had the same problem when I was trying to install Proxmox Backup Server on top of Debian 11. Commenting auto IPv6 config out in /etc/network/interfaces fixed the issue:
# iface enp0s25 inet6 auto

Strange thing is the interface (enp0s25) gets correct auto IPv6 configuration even with the line above commented out.
Two and a half years later... you saved me! I had the same issue with Proxmox 8.1.3
Thank you!
 
I have a similar issue, but the Ubuntu client is waiting for about a minute to start and still doesn't get a network interface.
The network is bridged and the router provides DHCP. It used to work fine for month but after a recent update the network problems started.
 
Last edited:
Same here, ipv6 commented out, this server was booting fine before and since this morning, stuck at that step! What can be done? Will this bad behaviour of Proxmox be ever fixed?
 
I have a similar issue, but the Ubuntu client is waiting for about a minute to start and still doesn't get a network interface.
The network is bridged and the router provides DHCP. It used to work fine for month but after a recent update the network problems started.
Just inc ase someone comes across this same issue, in my case it a bunch of firewall rules that were added to the host OS when installing docker which prevented the guest OSs to talk to the outside world or even get an IP address from the DHCP server.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!