Artifactory returns 404 for private GitHub Docker Repository

Describe the bug

Artifactory always returns 404 for private GitHub repo where my docker image is deployed.

Current behavior

When configuring a remote docker repository in Artifactory as following:

URL: https://ghcr.io//
Username: PAT Name
Password: PAT (with read:packages permission) -> also already tried to give all permissions, but still same behaviour

With this configuration always 404 is returned, with following error message:
Connection failed: Target remote URL returned error 404: Not Found

In the logs I can find following entry:

2024-05-16T16:25:08.269Z [jfrt ] [WARN ] [3507df68c5423496] [c.p.ResponseProcessCookies:130] [http-nio-8081-exec-8] - Invalid cookie header: "Set-Cookie: _octo=GH1.1.774614533.1715876708; domain=github.com; path=/; expires=Fri, 16 May 2025 16:25:08 GMT; secure; SameSite=Lax". Invalid 'expires' attribute: Fri, 16 May 2025 16:25:08 GMT
2024-05-16T16:25:08.611Z [jfrt ] [WARN ] [3507df68c5423496] [c.p.ResponseProcessCookies:130] [http-nio-8081-exec-8] - Invalid cookie header: "Set-Cookie: _octo=GH1.1.1649066562.1715876708; domain=github.com; path=/; expires=Fri, 16 May 2025 16:25:08 GMT; secure; SameSite=Lax". Invalid 'expires' attribute: Fri, 16 May 2025 16:25:08 GMT
2024-05-16T16:25:08.720Z [jfrt ] [WARN ] [3507df68c5423496] [.r.c.s.ResearchServiceImpl:290] [http-nio-8081-exec-8] - We were unable to check repoType, maybe it does not exist

Reproduction steps

No response

Expected behavior

No response

Setup JFrog CLI version

JFrog CLI version

Workflow operating system type and version

Kubernetes 1.29

JFrog Artifactory version (if relevant)

Helm Chart version: 107.84.10

JFrog Xray version (if relevant)

No response

Start by checking whether this repository handles the reported Artifactory configuration or whether the problem belongs to Artifactory or GitHub Container Registry. Reproduce the private-repository request using the stated URL and PAT permissions, then compare the result with the repository's documented setup and supported workflow. Done means a confirmed repository fix or a clearly documented reason the issue is out of scope.