[SOLVED] Repository is not signed / 403 Forbidden

[yuehan]

Dear all,

I had quite some years of experience with managing a large proxmox environment, however I stumble accross a stupid error I encountered for a simple lab setup of my new employer.

I setup a clean server with version 8.1. Everything works fine so far, however after adding the Proxmox no-subscription repository to the apt configuration and removing the enterprise repo, I fail to update the package lists.

Updating the package lists with 'apt-get update' leads to an error I cannot explain. Found similar entries in the forum, however most of the time, the issue were people with the enterprise repo configured, trying to update (HTTP 401). This is not the case in my setup.

E: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease  403  Forbidden [IP: 185.219.221.167 80]

E: The repository 'http://download.proxmox.com/debian/pve bookworm InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

EDIT: I verified, that the proxmox-release-bookworm.gpg key is in place in /etc/apt/trusted.gpg.d/ . Also tried to re-download the keyfile, but nothing changed regarding the problem.
Also manually trying to download http://download.proxmox.com/debian/pve/dists/bookworm/InRelease on the server via wget works fine.

Anyone stumbled accross a similar issue? There are no firewall restrictions in place, as far as I know, that could explain the issue. The repository configuration is as follows:

deb https://deb.debian.org/debian bookworm main contrib

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

# security updates
deb https://security.debian.org/debian-security bookworm-security main contrib

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

The ceph and enterprise repository definition in /etc/apt/sources.list.d/ were deleted by me. Any help is appreciated!

 

[tom]

Check https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories

=> Chapter 3.1.13

 

[yuehan]

Hi,

thanks for your response! I guess you posted it, while I was updating the description. As I used the proxmox image for installation, the key was already in place. I also tried to remove it and update it as described in 3.1.13, just in case, but the problem remains the same:

root@XXX:/etc/apt# wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg
--2024-05-17 16:18:43--  https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg
Resolving enterprise.proxmox.com (enterprise.proxmox.com)... 185.219.221.167, 2a01:7e0:0:424::249
Connecting to enterprise.proxmox.com (enterprise.proxmox.com)|185.219.221.167|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1187 (1.2K) [application/octet-stream]
Saving to: ‘/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg’

/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg  100%[===================================================================================================================>]   1.16K  --.-KB/s    in 0s

2024-05-17 16:18:43 (22.3 MB/s) - ‘/etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg’ saved [1187/1187]

root@XXX:/etc/apt# apt-get update
Err:1 http://download.proxmox.com/debian/pve bookworm InRelease
  403  Forbidden [IP: 51.91.38.34 80]
Hit:2 https://security.debian.org/debian-security bookworm-security InRelease
Hit:3 https://deb.debian.org/debian bookworm InRelease
Hit:4 https://deb.debian.org/debian bookworm-updates InRelease
Reading package lists... Done
E: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease  403  Forbidden [IP: 51.91.38.34 80]
E: The repository 'http://download.proxmox.com/debian/pve bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

 

[yuehan]

I digged deeper, as I just had access to the laboratory firewall and discovered an issue on the outer firewall, which was responsible for the problem. Still thanks for your input @tom !

Thanks and best regards,
yuehan