[SOLVED] Unable to update PVE from 7.3.3

diverk

New Member
Apr 5, 2026
2
0
0
Hello,

I'm very new to posting in forums, please excuse any incorrect protocol. I installed Proxmox in 2022 in a "homelab". I have no enterprise subscription. I am trying to update PVE to the latest stable version, and following recomendation, am trying to update to the latest version 7 before upgrading past that. I have disabled the enterprise repository in the GUI, and added the no-subscription repo. when I try the update (also using the GUI), the output shows errors resolving the repo locations. I have set the DNS options to 8.8.8.8, 9.9.9.9, and 1.1.1.1. Output below:

starting apt-get update
Err:1 http://ftp.us.debian.org/debian bullseye InRelease
Temporary failure resolving 'ftp.us.debian.org'
Err:2 http://security.debian.org bullseye-security InRelease
Temporary failure resolving 'security.debian.org'
Err:3 http://download.proxmox.com/debian/pve bullseye InRelease
Temporary failure resolving 'download.proxmox.com'
Err:4 http://ftp.us.debian.org/debian bullseye-updates InRelease
Temporary failure resolving 'ftp.us.debian.org'
Reading package lists...
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye/InRelease Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye-updates/InRelease Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease Temporary failure resolving 'download.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
TASK OK


Any help is appreciated,

Thank You
 
Thank You for the response! I set the DNS options in the GUI under network>DNS. Okay, so I found the problem. I changed my network router over a year ago, and it's at a different IP address. I could manually ping it (SSH'd into pve), but nothing external. I found the old setting in the gateway field, corrected it, and rebooted. All back on track; sorry for the bone-head post.