Fails to load ghcr

[bckelley]

Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

i get this error when I try to browse the ghcr repositories

Failed to get catalog of registry: Failed to get packages from registry 1, status=401

Expected Behavior

i thought id see the images from github, maybe I'm mistaken on how it works

Actual Behavior

Looping of trying to load and the same error

Steps to Reproduce

.

Portainer logs or screenshots

No response

Portainer version

2.33.1

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Docker version 28.3.3, build 980b856

OS and Architecture

Debian 13 (trixie)

Browser

Brave 1.81.136 (Official Build) (64-bit) Chromium: 139.0.7258.143

What command did you use to deploy Portainer?

services:
  portainer:
    image: portainer/portainer-ee:latest
    command: --license-key 2-XCAKctSMJ063aWCNBVPB4MgMI4mVGjJOJ0p0t9P5uMNMpYBdAOCE/SNHsTRvFjN4lXJG4Q4esAB018t0ghM=
    restart: unless-stopped
    ports:
      - 9443:9443
    volumes:
      - data:/data
      - /var/run/docker.sock:/var/run/docker.sock
volumes:
  data:

Additional Information

2025/08/27 03:11PM INF github.com/portainer/portainer-ee/api/http/handler/registries/registry_configure.go:191 > Flushed Helm registry cache due to configuration changes | context=RegistryConfigureHandler registry_id=1 registry_name=ghcr
2025/08/27 03:11PM INF github.com/portainer/portainer@v0.6.1-0.20241105012540-458d722d4754/pkg/libhelm/cache/cache.go:102 > Flushed registry client due to registry change | context=HelmRegistryCache registry_id=1
2025/08/27 03:11PM INF github.com/portainer/portainer-ee/api/http/handler/registries/registry_configure.go:191 > Flushed Helm registry cache due to configuration changes | context=RegistryConfigureHandler registry_id=1 registry_name=ghcr
2025/08/27 03:35PM INF github.com/portainer/portainer@v0.6.1-0.20241105012540-458d722d4754/pkg/libhelm/cache/cache.go:102 > Flushed registry client due to registry change | context=HelmRegistryCache registry_id=1
2025/08/27 03:35PM INF github.com/portainer/portainer-ee/api/http/handler/registries/registry_configure.go:191 > Flushed Helm registry cache due to configuration changes | context=RegistryConfigureHandler registry_id=1 registry_name=ghcr

[Nick-Portainer]

Hi @bckelley Has this worked before or is this your first time setup getting this error? Can you confirm the connection is using the correct credentials that have the correct permissions? - https://docs.portainer.io/admin/registries/add/ghcr

[bckelley]

Hi @bckelley Has this worked before or is this your first time setup getting this error? Can you confirm the connection is using the correct credentials that have the correct permissions? - https://docs.portainer.io/admin/registries/add/ghcr

this is my first time setting this up and that doc is less than helpful only because github has to change how they do thing every five seconds

done this with and without organization name

[Nick-Portainer]

Steps are as follows.

Generate a Personal Access token, this needs to be a Classic Token as we mention in our documentation we do not support fine grained tokens at this stage, then make sure the token has the correct permissions such as packages for your registry.

I just tested without issues.

[bckelley]

Would you mind updating with your steps as the steps in the repo are out of date with github

[Nick-Portainer]

Add Registry

Select Github

Generate Token

Confirm permissions

Enter Details and add the Registry to Portainer

Confirm you can access and browse the registry

[Nick-Portainer]

@bckelley How did you go?

[bckelley]

@bckelley How did you go?

Well I do sincerely apologize. It's not portainer once again bamboozled by github! and it's just a limitation on their end! thanks for you're help though!