no network after installing pve9 on trixie

T

tschmidt

Member
Oct 11, 2023
48
14
13
Im preparing to install pve9 on a preexisting debian trixie and currently do trial runs on throwaway installs.

I'm following https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie. After what seemed to be a success I unexpectedly lost network access to it.

Recreating the situation it seems that `apt install proxmox-ve postfix open-iscsi chrony` disables the networking service

Code: 
root@tschmidt-chimera:~# systemctl status networking
● networking.service - Raise network interfaces
     Loaded: loaded (/usr/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: active (exited) since Wed 2026-09-30 13:21:05 CEST; 16s ago
...
root@tschmidt-chimera:~# apt install proxmox-ve postfix open-iscsi chrony
...
root@tschmidt-chimera:~# systemctl status networking
● networking.service - Network initialization
     Loaded: loaded (/usr/lib/systemd/system/networking.service; disabled; preset: enabled)
     Active: active (exited) since Wed 2026-09-30 13:21:05 CEST; 3min 47s ago

(more specifically, installing ifupdown2 seems to do that)

And it doesn't seem to get reenabled later in the guide. Which means that when the install is next rebootet there wont be any network access to it. Which would be a major problem for me.

I can of course manually reenable the service to avoid that but the WHY remains. Am I doing it wrong/missing something? Is this a bug in the guide or package?
 
Hi, I could not reproduce this by following our guide.
Maybe check in your apt history and see the journal if something stands out?
 
tschmidt said:
Im preparing to install pve9 on a preexisting debian trixie and currently do trial runs on throwaway installs.

I'm following https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie. After what seemed to be a success I unexpectedly lost network access to it.

Recreating the situation it seems that `apt install proxmox-ve postfix open-iscsi chrony` disables the networking service

Code: 
root@tschmidt-chimera:~# systemctl status networking
● networking.service - Raise network interfaces
     Loaded: loaded (/usr/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: active (exited) since Wed 2026-09-30 13:21:05 CEST; 16s ago
...
root@tschmidt-chimera:~# apt install proxmox-ve postfix open-iscsi chrony
...
root@tschmidt-chimera:~# systemctl status networking
● networking.service - Network initialization
     Loaded: loaded (/usr/lib/systemd/system/networking.service; disabled; preset: enabled)
     Active: active (exited) since Wed 2026-09-30 13:21:05 CEST; 3min 47s ago

(more specifically, installing ifupdown2 seems to do that)

And it doesn't seem to get reenabled later in the guide. Which means that when the install is next rebootet there wont be any network access to it. Which would be a major problem for me.

I can of course manually reenable the service to avoid that but the WHY remains. Am I doing it wrong/missing something? Is this a bug in the guide or package?
Click to expand...
Maybe you can try to do the network pinning ?
During the installation did you do "apt upgrade" ?
 
It seems to have something to do with the debian packages we install by default. At least I can't reproduce it on plain debian. I didn't think any of those would affect basic networking (We still use ifupdown same as plain debian). I need to look into this some more.

The interface names stay the same so I doubt it got something to do with pinning.

No, I did not run `upgrade`. Just `update` & `full-upgrade`.
 
Last edited:
The host im ultimately trying to switch to proxmox is already running debian and can't be easily reinstalled. The throwaways use the same packages/config to simulate this.

But as I said *I* am good. I simply want to prevent others running into the same problem.
 
  • Like
Reactions: ghusson
You must log in or register to reply here.
Top Bottom
Back