Proxmox Backup Server installation stuck #1396

@MickLesk commented on GitHub (Jun 30, 2025):

thats an simple debian package with following install:
curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg"
cat <>/etc/apt/sources.list
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription
EOF
apt-get update
apt-get install -y proxmox-backup-server

do it manually on this lxc and check

@MickLesk commented on GitHub (Jun 30, 2025): thats an simple debian package with following install: curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg" cat <<EOF >>/etc/apt/sources.list deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription EOF apt-get update apt-get install -y proxmox-backup-server do it manually on this lxc and check

saavagebueno commented

@yushisora commented on GitHub (Jun 30, 2025):

Okay, I am sorry but I didn't actually use the default settings instead I set the hostname to pbs from the default proxmox-backup-server and the remaining settings keep the same. Now that I try the real default settings the script runs fine and I have my pbs installed and setup nicely.

But I wonder why the issue occur when I try to use a different hostname?

@yushisora commented on GitHub (Jun 30, 2025): Okay, I am sorry but I didn't actually use the default settings instead I set the hostname to `pbs` from the default `proxmox-backup-server` and the remaining settings keep the same. Now that I try the real default settings the script runs fine and I have my pbs installed and setup nicely. But I wonder why the issue occur when I try to use a different hostname?

saavagebueno commented

@MickLesk commented on GitHub (Jun 30, 2025):

idk, the hostname is an network thing. maybe your router dont allow this as special name or proxmox himself

@MickLesk commented on GitHub (Jun 30, 2025): idk, the hostname is an network thing. maybe your router dont allow this as special name or proxmox himself

saavagebueno commented

@yushisora commented on GitHub (Jun 30, 2025):

Alright, that make sense. Thanks for the help.

@yushisora commented on GitHub (Jun 30, 2025): Alright, that make sense. Thanks for the help.

saavagebueno commented

@Crypto-Spartan commented on GitHub (Jul 4, 2025):

This issue still exists. I used the advanced install to set a MAC address and VLAN, left the hostname alone. But I still have the exact same issue.

edit: also using verbose mode

@Crypto-Spartan commented on GitHub (Jul 4, 2025): This issue still exists. I used the advanced install to set a MAC address and VLAN, left the hostname alone. But I still have the exact same issue. edit: also using verbose mode

saavagebueno commented

@Crypto-Spartan commented on GitHub (Jul 4, 2025):

Tried to follow @MickLesk 's instructions, but it's still stuck:

root@proxmox-backup-server:~# curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg" 
root@proxmox-backup-server:~# cat /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib

deb http://deb.debian.org/debian bookworm-updates main contrib

deb http://security.debian.org bookworm-security main contrib

deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription
root@proxmox-backup-server:~# apt update 
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://download.proxmox.com/debian/pbs bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@proxmox-backup-server:~# apt install -y proxmox-backup
proxmox-backup                      proxmox-backup-client-dbgsym        proxmox-backup-file-restore         proxmox-backup-server
proxmox-backup-client               proxmox-backup-docs                 proxmox-backup-file-restore-dbgsym  proxmox-backup-server-dbgsym
root@proxmox-backup-server:~# apt install -y proxmox-backup-server
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 11032 (apt-get)... 42s

@Crypto-Spartan commented on GitHub (Jul 4, 2025): Tried to follow @MickLesk 's instructions, but it's still stuck: ``` root@proxmox-backup-server:~# curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg" root@proxmox-backup-server:~# cat /etc/apt/sources.list deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib deb http://security.debian.org bookworm-security main contrib deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription root@proxmox-backup-server:~# apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://download.proxmox.com/debian/pbs bookworm InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@proxmox-backup-server:~# apt install -y proxmox-backup proxmox-backup proxmox-backup-client-dbgsym proxmox-backup-file-restore proxmox-backup-server proxmox-backup-client proxmox-backup-docs proxmox-backup-file-restore-dbgsym proxmox-backup-server-dbgsym root@proxmox-backup-server:~# apt install -y proxmox-backup-server Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 11032 (apt-get)... 42s ```

saavagebueno commented

@SirMartin commented on GitHub (Jul 5, 2025):

I think this issue should be reopened.

I am trying to install with advance settings and if I try to install it a privileged container is always stuck, once I tried on verbose too, and it's stuck on the same place, if it's not verbose it's stuck under Installing Proxmox Backup Server. I tried multiple times, different nodes, and always the same, can stay hours there. But I just use default settings and nothing changes, it works like a charm.

@SirMartin commented on GitHub (Jul 5, 2025): I think this issue should be reopened. I am trying to install with advance settings and if I try to install it a privileged container is always stuck, once I tried on verbose too, and it's stuck on the same place, if it's not verbose it's stuck under Installing Proxmox Backup Server. I tried multiple times, different nodes, and always the same, can stay hours there. But I just use default settings and nothing changes, it works like a charm.

saavagebueno commented

@yushisora commented on GitHub (Jul 5, 2025):

@MickLesk I think we should reopen this issue. I also edited the original post to show that I am using advanced setting instead.

@yushisora commented on GitHub (Jul 5, 2025): @MickLesk I think we should reopen this issue. I also edited the original post to show that I am using advanced setting instead.

saavagebueno commented

@MickLesk commented on GitHub (Jul 5, 2025):

@tremor021 can you check?

@MickLesk commented on GitHub (Jul 5, 2025): @tremor021 can you check?

saavagebueno commented

@tremor021 commented on GitHub (Jul 5, 2025):

all is good here

@tremor021 commented on GitHub (Jul 5, 2025): <img width="930" height="560" alt="Image" src="https://github.com/user-attachments/assets/dd5810c4-c2b6-4ef8-b807-ddbfcd24cfda" /> all is good here

saavagebueno commented

@SirMartin commented on GitHub (Jul 5, 2025):

Yea, as unpriviliged, the issues are with advanced settings, in my case trying to have one with privileges

@SirMartin commented on GitHub (Jul 5, 2025): Yea, as unpriviliged, the issues are with advanced settings, in my case trying to have one with privileges

saavagebueno commented

@tremor021 commented on GitHub (Jul 5, 2025):

All ok with priviledged LXC

@tremor021 commented on GitHub (Jul 5, 2025): <img width="848" height="802" alt="Image" src="https://github.com/user-attachments/assets/3c646ace-5d69-4009-9388-ff9105d56691" /> All ok with priviledged LXC

saavagebueno commented

@MickLesk commented on GitHub (Jul 5, 2025):

Work fine Here, both Settings

@MickLesk commented on GitHub (Jul 5, 2025): Work fine Here, both Settings

saavagebueno commented

@Shadowfita commented on GitHub (Jul 8, 2025):

Im getting the same hang on the same spot when using advanced settings to change the network bridge.

@Shadowfita commented on GitHub (Jul 8, 2025): Im getting the same hang on the same spot when using advanced settings to change the network bridge.

saavagebueno commented

@Crypto-Spartan commented on GitHub (Jul 9, 2025):

mine is still hanging. i can reliably reproduce this issue 100% of the time. if you need logs/data, let me know and i can provide it. here's the config (with some fields omitted for privacy):
(note that i set a custom MAC address and VLAN, also changed the values for CPU & RAM)

it succesfully updates the container OS:

then it stays stuck here indefinitely:

@Crypto-Spartan commented on GitHub (Jul 9, 2025): mine is still hanging. i can reliably reproduce this issue 100% of the time. if you need logs/data, let me know and i can provide it. here's the config (with some fields omitted for privacy): (note that i set a custom MAC address and VLAN, also changed the values for CPU & RAM) <img width="1017" height="902" alt="Image" src="https://github.com/user-attachments/assets/ac73cd51-7ea9-4e4a-8049-a135aad137d4" /> **it succesfully updates the container OS**: <img width="983" height="980" alt="Image" src="https://github.com/user-attachments/assets/23513771-b395-4c95-82e0-f3bb64a997c6" /> **then it stays stuck here indefinitely:** <img width="1054" height="984" alt="Image" src="https://github.com/user-attachments/assets/8250a110-d6e4-4979-ae62-b3e0a284c610" />

saavagebueno commented

@Crypto-Spartan commented on GitHub (Jul 9, 2025):

When i eventually killed the container after waiting for a long time, this was the error it showed, unsure if it's helpful:

@Crypto-Spartan commented on GitHub (Jul 9, 2025): When i eventually killed the container after waiting for a long time, this was the error it showed, unsure if it's helpful: <img width="2292" height="153" alt="Image" src="https://github.com/user-attachments/assets/7afc9d70-bad1-4dd5-9415-2de4805f550a" />

saavagebueno commented

@Crypto-Spartan commented on GitHub (Jul 9, 2025):

@MickLesk @tremor021

Please re-open this issue as there have been multiple user reports now that this is an ongoing problem

@Crypto-Spartan commented on GitHub (Jul 9, 2025): @MickLesk @tremor021 Please re-open this issue as there have been multiple user reports now that this is an ongoing problem

saavagebueno commented

@MickLesk commented on GitHub (Jul 9, 2025):

then find the solution, the script work fine.

Then use default and increase the values after all

@MickLesk commented on GitHub (Jul 9, 2025): then find the solution, the script work fine. Then use default and increase the values after all

saavagebueno commented

@tremor021 commented on GitHub (Jul 9, 2025):

@Crypto-Spartan i'm not really sure what you want us to say more here? I can't reproduce your issue. No matter how many times i try reinstalling on both my home and work node, it all works fine.

Just because someone else has the same issue as you, it just means your hosts share the same problem, it doesn't mean that the script has issues.

@tremor021 commented on GitHub (Jul 9, 2025): @Crypto-Spartan i'm not really sure what you want us to say more here? I can't reproduce your issue. No matter how many times i try reinstalling on both my home and work node, it all works fine. Just because someone else has the same issue as you, it just means your hosts share the same problem, it doesn't mean that the script has issues.

saavagebueno commented

@bezibaerchen commented on GitHub (Aug 8, 2025):

I am in the same boat. Advanced settings, set different bridge and configured as privileged. Neglected VAAPI part

When logging on to the lxc I can see obviously stuck apt-processes:

root 1283 0.0 0.2 8776 5096 pts/3 Ss+ 14:52 0:00 bash -c #!/usr/bin/env bash # Copyright (c) 2021-2025 tteck # Author: tteck (tteckster) # License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE # Source: https://www.proxmox.com/en/proxmox-backup-server source /dev/stdin <<<"$FUNCTIONS_FILE_PATH" color verb_ip6 catch_errors setting_up_container network_check update_os msg_info "Installing Proxmox Backup Server" curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg" cat <<EOF >>/etc/apt/sources.list deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription EOF $STD apt-get update $STD apt-get install -y proxmox-backup-server msg_ok "Installed Proxmox Backup Server" motd_ssh customize msg_info "Cleaning up" $STD apt-get -y autoremove $STD apt-get -y autoclean msg_ok "Cleaned" root 11104 0.0 2.9 72524 62044 pts/3 S+ 14:53 0:01 apt-get install -y proxmox-backup-server

@bezibaerchen commented on GitHub (Aug 8, 2025): <img width="1272" height="824" alt="Image" src="https://github.com/user-attachments/assets/43dbb94a-c154-49df-9f96-c36d07da05be" /> I am in the same boat. Advanced settings, set different bridge and configured as privileged. Neglected VAAPI part When logging on to the lxc I can see obviously stuck apt-processes: `root 1283 0.0 0.2 8776 5096 pts/3 Ss+ 14:52 0:00 bash -c #!/usr/bin/env bash # Copyright (c) 2021-2025 tteck # Author: tteck (tteckster) # License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE # Source: https://www.proxmox.com/en/proxmox-backup-server source /dev/stdin <<<"$FUNCTIONS_FILE_PATH" color verb_ip6 catch_errors setting_up_container network_check update_os msg_info "Installing Proxmox Backup Server" curl -fsSL "https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg" -o "/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg" cat <<EOF >>/etc/apt/sources.list deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription EOF $STD apt-get update $STD apt-get install -y proxmox-backup-server msg_ok "Installed Proxmox Backup Server" motd_ssh customize msg_info "Cleaning up" $STD apt-get -y autoremove $STD apt-get -y autoclean msg_ok "Cleaned" root 11104 0.0 2.9 72524 62044 pts/3 S+ 14:53 0:01 apt-get install -y proxmox-backup-server`

saavagebueno commented

@stevecopeza commented on GitHub (Aug 11, 2025):

Is this possibly to do with trying to install PBS v4 on a PVE v8 server ?

@stevecopeza commented on GitHub (Aug 11, 2025): Is this possibly to do with trying to install PBS v4 on a PVE v8 server ?

saavagebueno commented

@joshft91 commented on GitHub (Aug 16, 2025):

I'm having this as well. The only thing I changed in the advanced settings is to use a privileged container. The rest were defaults and I didn't set a root password. Got stuck on the "installing Proxmox backup server".

Edit: after using verbose mode, I'm also stuck on the Reloading network config on first install part. I have 10.0.0.x IP pool, but I can't imagine that would cause any issues.

Edit2: Not privileged related, I get the same issue when trying and advanced install with all default values.

@joshft91 commented on GitHub (Aug 16, 2025): I'm having this as well. The only thing I changed in the advanced settings is to use a privileged container. The rest were defaults and I didn't set a root password. Got stuck on the "installing Proxmox backup server". Edit: after using verbose mode, I'm also stuck on the `Reloading network config on first install` part. I have `10.0.0.x` IP pool, but I can't imagine that would cause any issues. Edit2: Not privileged related, I get the same issue when trying and advanced install with all default values.

saavagebueno commented

@Crypto-Spartan commented on GitHub (Aug 19, 2025):

Edit2: Not privileged related, I get the same issue when trying and advanced install with all default values.

This has been my experience as well. There's something that's different enough with using the advanced that it's causing issues.

@Crypto-Spartan commented on GitHub (Aug 19, 2025): > Edit2: Not privileged related, I get the same issue when trying and advanced install with all default values. This has been my experience as well. There's something that's different enough with using the advanced that it's causing issues.

saavagebueno commented

@MickLesk commented on GitHub (Aug 20, 2025):

It happens because ifupdown2 tries to reload the network inside the LXC during installation, which can hang depending on advanced network settings (bridge, VLAN, MAC) since the interfaces are actually managed by the Proxmox host.

You can try after merge of:
https://github.com/community-scripts/ProxmoxVE/pull/7013

@MickLesk commented on GitHub (Aug 20, 2025): It happens because ifupdown2 tries to reload the network inside the LXC during installation, which can hang depending on advanced network settings (bridge, VLAN, MAC) since the interfaces are actually managed by the Proxmox host. You can try after merge of: https://github.com/community-scripts/ProxmoxVE/pull/7013

saavagebueno commented

@joshft91 commented on GitHub (Aug 20, 2025):

It happens because ifupdown2 tries to reload the network inside the LXC during installation, which can hang depending on advanced network settings (bridge, VLAN, MAC) since the interfaces are actually managed by the Proxmox host.

You can try after merge of: #7013

I saw it was merged in and tried again, but it still appears to be hanging. I don't know enough about network interfaces to be much on the technical side, but are there any commands I can run on my Proxmox host to help narrow this down and why it might be causing issues for some users, but not all (like you)?

Happy to send over any other information that would help debug this issue; it's odd that I don't have this issue with a regular install, but only default (without making any changes other than the verbose setting)

Edit: I ran a regular install (verbose) and advanced (verbose) and entered through everything with default settings and compared log outputs... it's pulling in the same things it seems like. Everything is identical except some of the starting output due to the advanced selection.

@joshft91 commented on GitHub (Aug 20, 2025): > It happens because ifupdown2 tries to reload the network inside the LXC during installation, which can hang depending on advanced network settings (bridge, VLAN, MAC) since the interfaces are actually managed by the Proxmox host. > > You can try after merge of: [#7013](https://github.com/community-scripts/ProxmoxVE/pull/7013) I saw it was merged in and tried again, but it still appears to be hanging. I don't know enough about network interfaces to be much on the technical side, but are there any commands I can run on my Proxmox host to help narrow this down and why it might be causing issues for some users, but not all (like you)? Happy to send over any other information that would help debug this issue; it's odd that I don't have this issue with a regular install, but only default (without making any changes other than the verbose setting) Edit: I ran a regular install (verbose) and advanced (verbose) and entered through everything with default settings and compared log outputs... it's pulling in the same things it seems like. Everything is identical except some of the starting output due to the advanced selection.

saavagebueno commented

@MickLesk commented on GitHub (Aug 20, 2025):

Enter these commands on your host, replace ctid with your lxc id (from the hanging install)

pct exec -- ip a

pct config | grep net

pct exec -- ps aux | grep ifreload

ls -l /sys/class/net | grep veth

brctl show # (or 'bridge link show' on newer systems)

@MickLesk commented on GitHub (Aug 20, 2025): Enter these commands on your host, replace ctid with your lxc id (from the hanging install) pct exec <CTID> -- ip a pct config <CTID> | grep net pct exec <CTID> -- ps aux | grep ifreload ls -l /sys/class/net | grep veth brctl show # (or 'bridge link show' on newer systems)

saavagebueno commented

@joshft91 commented on GitHub (Aug 20, 2025):

Here's the outputs of those commands. I did both brctl show # and bridge link show at the end as well. Thank you!

root@proxmox01:~# pct exec 102 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0@if59: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether bc:24:11:b4:be:db brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.0.0.85/24 brd 10.0.0.255 scope global dynamic eth0
       valid_lft 86289sec preferred_lft 86289sec
    inet6 fe80::be24:11ff:feb4:bedb/64 scope link 
       valid_lft forever preferred_lft forever

root@proxmox01:~# pct config 102 | grep net
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:B4:BE:DB,ip=dhcp,ip6=auto,type=veth

root@proxmox01:~# pct exec 102 ps aux | grep ifreload
root       11893  0.0  2.0 200648 42864 pts/4    Sl+  09:48   0:00 python3 /usr/sbin/ifreload -a

root@proxmox01:~# ls -l /sys/class/net | grep veth
lrwxrwxrwx 1 root root    0 Aug 16 17:52 veth101i0 -> ../../devices/virtual/net/veth101i0
lrwxrwxrwx 1 root root    0 Aug 20 09:47 veth102i0 -> ../../devices/virtual/net/veth102i0
lrwxrwxrwx 1 root root    0 Aug 16 17:52 veth103i0 -> ../../devices/virtual/net/veth103i0
lrwxrwxrwx 1 root root    0 Aug 16 17:52 veth104i0 -> ../../devices/virtual/net/veth104i0
lrwxrwxrwx 1 root root    0 Aug 16 17:52 veth105i0 -> ../../devices/virtual/net/veth105i0

root@proxmox01:~# brctl show #
bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.e8ff1ed1f285       no              enp1s0
                                                        tap100i0
                                                        veth101i0
                                                        veth102i0
                                                        veth103i0
                                                        veth104i0
                                                        veth105i0
root@proxmox01:~# bridge link show
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 100 
5: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 
6: veth101i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 
7: veth103i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 
8: veth104i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 
9: veth105i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 
59: veth102i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2

@joshft91 commented on GitHub (Aug 20, 2025): Here's the outputs of those commands. I did both `brctl show #` and `bridge link show` at the end as well. Thank you! ``` root@proxmox01:~# pct exec 102 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: eth0@if59: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether bc:24:11:b4:be:db brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.0.0.85/24 brd 10.0.0.255 scope global dynamic eth0 valid_lft 86289sec preferred_lft 86289sec inet6 fe80::be24:11ff:feb4:bedb/64 scope link valid_lft forever preferred_lft forever ``` ``` root@proxmox01:~# pct config 102 | grep net net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:B4:BE:DB,ip=dhcp,ip6=auto,type=veth ``` ``` root@proxmox01:~# pct exec 102 ps aux | grep ifreload root 11893 0.0 2.0 200648 42864 pts/4 Sl+ 09:48 0:00 python3 /usr/sbin/ifreload -a ``` ``` root@proxmox01:~# ls -l /sys/class/net | grep veth lrwxrwxrwx 1 root root 0 Aug 16 17:52 veth101i0 -> ../../devices/virtual/net/veth101i0 lrwxrwxrwx 1 root root 0 Aug 20 09:47 veth102i0 -> ../../devices/virtual/net/veth102i0 lrwxrwxrwx 1 root root 0 Aug 16 17:52 veth103i0 -> ../../devices/virtual/net/veth103i0 lrwxrwxrwx 1 root root 0 Aug 16 17:52 veth104i0 -> ../../devices/virtual/net/veth104i0 lrwxrwxrwx 1 root root 0 Aug 16 17:52 veth105i0 -> ../../devices/virtual/net/veth105i0 ``` ``` root@proxmox01:~# brctl show # bridge name bridge id STP enabled interfaces vmbr0 8000.e8ff1ed1f285 no enp1s0 tap100i0 veth101i0 veth102i0 veth103i0 veth104i0 veth105i0 root@proxmox01:~# bridge link show 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 100 5: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 6: veth101i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 7: veth103i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 8: veth104i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 9: veth105i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 59: veth102i0@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master vmbr0 state forwarding priority 32 cost 2 ```

saavagebueno commented

@spyder94 commented on GitHub (Aug 20, 2025):

I was finally able to get the Advanced installation to work today. The only thing I did different from the several other attempts was disable IPv6. The only other option I changed in the Advanced settings was to choose Privileged at the first step. I'm guessing since the installation hangs on the installation of ifupdown2 that it has something to do with some networking config.

On a separate note, while I appreciate the fact that this problem isn't a problem with the script itself, I don't think it very much "community" like to just say, "it works on my machine" and to tell someone asking for assistance to "find the solution". Not faulting anyone for not having an answer, but just closing this out when obviously there are many people experiencing the problem makes it more difficult for the community to find a solution together.

@spyder94 commented on GitHub (Aug 20, 2025): I was finally able to get the Advanced installation to work today. The only thing I did different from the several other attempts was disable IPv6. The only other option I changed in the Advanced settings was to choose Privileged at the first step. I'm guessing since the installation hangs on the installation of ifupdown2 that it has something to do with some networking config. On a separate note, while I appreciate the fact that this problem isn't a problem with the script itself, I don't think it very much "community" like to just say, "it works on my machine" and to tell someone asking for assistance to "find the solution". Not faulting anyone for not having an answer, but just closing this out when obviously there are many people experiencing the problem makes it more difficult for the community to find a solution together.

saavagebueno commented

@joshft91 commented on GitHub (Aug 20, 2025):

The only thing I did different from the several other attempts was disable IPv6

Oh wow, I just did this (with the exact same config as above) , except disabling IPv6 and this just went through for me as a privileged LXC container. Thank you!

@MickLesk Hopefully that helps you narrow any potential issues between the standard and default install.

@joshft91 commented on GitHub (Aug 20, 2025): > The only thing I did different from the several other attempts was disable IPv6 Oh wow, I just did this (with the exact same config as above) , except disabling IPv6 and this just went through for me as a privileged LXC container. Thank you! @MickLesk Hopefully that helps you narrow any potential issues between the standard and default install.

saavagebueno commented

@Crypto-Spartan commented on GitHub (Aug 21, 2025):

On a separate note, while I appreciate the fact that this problem isn't a problem with the script itself, I don't think it very much "community" like to just say, "it works on my machine" and to tell someone asking for assistance to "find the solution". Not faulting anyone for not having an answer, but just closing this out when obviously there are many people experiencing the problem makes it more difficult for the community to find a solution together.

In this thread it seems there are enough people saying "it doesn't work on my machine" that it indicates something may need to be changed with the script, even if it works on other people's machines. If a solution works in some places but fails in many others, I would argue it's worth exploring some alternative solutions so that it may be possible for it to work on almost every machine.

@Crypto-Spartan commented on GitHub (Aug 21, 2025): > On a separate note, while I appreciate the fact that this problem isn't a problem with the script itself, I don't think it very much "community" like to just say, "it works on my machine" and to tell someone asking for assistance to "find the solution". Not faulting anyone for not having an answer, but just closing this out when obviously there are many people experiencing the problem makes it more difficult for the community to find a solution together. In this thread it seems there are enough people saying "it doesn't work on my machine" that it indicates _something_ may need to be changed with the script, even if it works on other people's machines. If a solution works in some places but fails in many others, I would argue it's worth exploring some alternative solutions so that it may be possible for it to work on _almost_ every machine.

saavagebueno commented

@MickLesk commented on GitHub (Aug 21, 2025):

Guys, what are you actually trying to achieve here? I have fixed the script 3 times. This is a simple curl from Proxmox itself. (Import gpg, APT Update, APT Install). What are we supposed to do here? If I can't recreate it, no matter what I do, I can only fix it blindly and I've done that 3 times. Slamming accusations in here that we don't care is outrageous. Be glad that we do this for hours every day. Gratitude sometimes looks different.

@MickLesk commented on GitHub (Aug 21, 2025): Guys, what are you actually trying to achieve here? I have fixed the script 3 times. This is a simple curl from Proxmox itself. (Import gpg, APT Update, APT Install). What are we supposed to do here? If I can't recreate it, no matter what I do, I can only fix it blindly and I've done that 3 times. Slamming accusations in here that we don't care is outrageous. Be glad that we do this for hours every day. Gratitude sometimes looks different.

saavagebueno commented

@spyder94 commented on GitHub (Aug 21, 2025):

The points I was trying to make are 1) some of the phrasings aren't helpful and tend to come across as rather unfriendly and 2) more importantly, closing the ticket when many people are still having issues makes it so the ticket doesn't show up in the default issues list. Therefore, fewer people who may be able to help are going to see the ticket. That means it may take a longer to find a resolution and can also lead to duplicate tickets being created. I'm extremely appreciative to any and everyone who contributes to communities like this.

@spyder94 commented on GitHub (Aug 21, 2025): The points I was trying to make are 1) some of the phrasings aren't helpful and tend to come across as rather unfriendly and 2) more importantly, closing the ticket when many people are still having issues makes it so the ticket doesn't show up in the default issues list. Therefore, fewer people who may be able to help are going to see the ticket. That means it may take a longer to find a resolution and can also lead to duplicate tickets being created. I'm extremely appreciative to any and everyone who contributes to communities like this.

saavagebueno commented

@tremor021 commented on GitHub (Aug 21, 2025):

In this thread it seems there are enough people saying "it doesn't work on my machine" that it indicates something may need to be changed with the script, even if it works on other people's machines. If a solution works in some places but fails in many others, I would argue it's worth exploring some alternative solutions so that it may be possible for it to work on almost every machine.

I'm not sure what your point is. You can have 100 people installing, 90 have no issues, 10 have. This doesnt mean a script is bad, it means 10 people did something wrong or their hosts have issues. We tried implementing things differently, thinking it could be the possible issue, but on our hosts it keeps working, with fixes or without them. So its not the script issue, its your hosts/networks/or whatever it might be.

@tremor021 commented on GitHub (Aug 21, 2025): > In this thread it seems there are enough people saying "it doesn't work on my machine" that it indicates _something_ may need to be changed with the script, even if it works on other people's machines. If a solution works in some places but fails in many others, I would argue it's worth exploring some alternative solutions so that it may be possible for it to work on _almost_ every machine. I'm not sure what your point is. You can have 100 people installing, 90 have no issues, 10 have. This doesnt mean a script is bad, it means 10 people did something wrong or their hosts have issues. We tried implementing things differently, thinking it could be the possible issue, but on our hosts it keeps working, with fixes or without them. So its not the script issue, its your hosts/networks/or whatever it might be.

saavagebueno commented

@Crypto-Spartan commented on GitHub (Aug 21, 2025):

I'm not sure what your point is. You can have 100 people installing, 90 have no issues, 10 have. This doesnt mean a script is bad, it means 10 people did something wrong or their hosts have issues. We tried implementing things differently, thinking it could be the possible issue, but on our hosts it keeps working, with fixes or without them. So its not the script issue, its your hosts/networks/or whatever it might be.

@tremor021 then can you explain why multiple people in this thread have reported that using the default option works, but if you use the advanced config and then select the default for every option, it fails? To me it seems that there's a weird difference between these 2 options which is causing issues for many of us.

@Crypto-Spartan commented on GitHub (Aug 21, 2025): > I'm not sure what your point is. You can have 100 people installing, 90 have no issues, 10 have. This doesnt mean a script is bad, it means 10 people did something wrong or their hosts have issues. We tried implementing things differently, thinking it could be the possible issue, but on our hosts it keeps working, with fixes or without them. So its not the script issue, its your hosts/networks/or whatever it might be. @tremor021 then can you explain why multiple people in this thread have reported that using the default option works, but if you use the advanced config and then select the default for every option, it fails? To me it seems that there's a weird difference between these 2 options which is causing issues for many of us.

saavagebueno commented

@scheperr commented on GitHub (Aug 26, 2025):

YES! Disabling IPv6 in advanced config does the trick, even for unprivileged!

@scheperr commented on GitHub (Aug 26, 2025): YES! Disabling IPv6 in advanced config does the trick, even for unprivileged!

saavagebueno commented