Update from proxmox-ve: 5.1-42 to 5.2 Problem

williwinkie

Active Member
Jan 24, 2018
6
0
41
Olsberg
Hi proxmox updates have always worked perfectly until now....

starting apt-get update
Ign:1 htps://enterprise.proxmox.com/debian/pve stretch InRelease
Err:2 htps://enterprise.proxmox.com/debian/pve stretch Release
Received HTTP code 503 from proxy after CONNECT
Ign:3 htp://ftp.de.debian.org/debian stretch InRelease
Get:4 htp://ftp.de.debian.org/debian stretch Release [118 kB]
Get:6 htp://security.debian.org stretch/updates InRelease [94.3 kB]
Reading package lists...
E: The repository 'htps://enterprise.proxmox.com/debian/pve stretch Release' does no longer have a Release file.
E: Release file for htp://security.debian.org/dists/stretch/updates/InRelease is expired (invalid since 1d 16h 38min 18s). Updates for this repository will not be applied.
TASK ERROR: command 'apt-get update' failed: exit code 100

Any ideas
Thanks
Tony
 
Ign:1 htps://enterprise.proxmox.com/debian/pve stretch InRelease
Err:2 htps://enterprise.proxmox.com/debian/pve stretch Release
Did you remove the 't'? Try it again.
 
Thanks Alwin, I took out the "t" because of "posting links" restrictions.
Try again ------
starting apt-get update
Ign:1 https://enterprise.proxmox.com/debian/pve stretch InRelease
Err:2 https://enterprise.proxmox.com/debian/pve stretch Release
Received HTTP code 503 from proxy after CONNECT
Get:3 http://security.debian.org stretch/updates InRelease [94.3 kB]
Ign:4 http://ftp.de.debian.org/debian stretch InRelease
Get:5 http://ftp.de.debian.org/debian stretch Release [118 kB]
Reading package lists...
E: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does no longer have a Release file.
E: Release file for http://security.debian.org/dists/stretch/updates/InRelease is expired (invalid since 2d 15h 34min 8s). Updates for this repository will not be applied.
TASK ERROR: command 'apt-get update' failed: exit code 100
 
Sorry about the long delay ...:(
Thanks to you Alwin my updates are working again - and yes it was a proxy/firewall problem not Proxmox...
Changed to another proxy and it worked

Thanks