Proxmox Install failed

[aaronpbrown]

Cannot get the single line Proxmox installed, I run into errors on the repositories, whether selecting ver 12 or 13 for Debian... :(

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Installing Dependencies
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[INFO] Updating package lists...
E: The repository 'http://deb.debian.org/debian trixie Release' no longer has a Release file.
E: The repository 'http://deb.debian.org/debian trixie-updates Release' no longer has a Release file.
E: The repository 'http://security.debian.org trixie-security Release' no longer has a Release file.

[ERROR] Installation failed. Check the output above for errors.

--

[INFO] Updating package lists...
E: The repository 'http://deb.debian.org/debian bookworm Release' no longer has a Release file.
E: The repository 'http://deb.debian.org/debian bookworm-updates Release' no longer has a Release file.
E: The repository 'http://security.debian.org bookworm-security Release' no longer has a Release file.

[tvancott42]

Hey @aaronpbrown, this is a networking issue inside the LXC container, not a script problem. Both Debian 12 and 13 repos are active and working (bookworm just had a point release last month), and the fact that both versions fail with the same error is the telltale - if it were a repo issue, it'd be version-specific. The container just can't reach the internet to pull packages.

A few things to check (replace <CT_ID> with your container ID):

First, try running apt-get update directly on the Proxmox host. If that also fails, the issue is at the host level and not specific to the container.

If the host is fine, check what's going on inside the container:

# Is DNS configured?
pct exec <CT_ID> -- cat /etc/resolv.conf

# Can the container actually reach the internet?
pct exec <CT_ID> -- ping -c 3 deb.debian.org

# Is there a default route?
pct exec <CT_ID> -- ip route

If you're using DHCP, the container might not be getting proper DNS or gateway info from your DHCP server. And if you have any firewall rules restricting outbound traffic from certain VLANs (pretty common in UniFi setups with tighter security), the container could be getting blocked from reaching the Debian repos.

Let me know what you find and we'll get it sorted out.