Proxmox can't connect to community scripts.

[JorgeAnzola]

I'm pretty new with Proxmox. It was all running great, and suddenly I couldn't run scripts anymore. I'm not sure what I could have changed to trigger this. At first I thought it was an error with a particular script, but it happens with all of them.

This is the output I'm getting when trying to install Dockge with the script. Please let me know if I'd need to verbose it, but it's all green until that same error.

   / __ \____  _____/ /______ ____

  / / / / __ \/ ___/ //_/ __ `/ _ \

 / /_/ / /_/ / /__/ ,< / /_/ /  __/

/_____/\____/\___/_/|_|\__, /\___/

                      /____/      

  ⚙️  Using Default Settings on node pve

    Container ID: 115

  ️  Operating System: debian (12)

    Container Type: Unprivileged

    Disk Size: 18 GB

    CPU Cores: 2

  ️  RAM Size: 2048 MiB

    Creating a Dockge LXC using the above default settings

 

  ✔️   Validated Storage (rootdir / vztmpl).

  ✔️   LXC Template List Updated

  ✔️   Started LXC Container

  ✔️   Customized LXC Container

  ✔️   Set up Container OS

  ✔️   Network Connected: 192.168.2.102 2a02:a441:9e94:**** fd4e:3732:3530:0:****

  ✔️   IPv4 Internet Connected

  ✔️   IPv6 Internet Connected

  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )

  ✔️   Updated Container OS

curl: (22) The requested URL returned error: 403



[ERROR] in line 20: exit code 0: while executing command DOCKER_LATEST_VERSION=$(get_latest_release "moby/moby")



[ERROR] in line 1249: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/"$var_install".sh)" $?

I've tried a few things, I have Pihole, I stopped using it to test.

I also tried cloning the scripts repo into Bitbucket.

I tried these two call, just to check what's going on.

root@pve:~# curl -I https://github.com

HTTP/2 200 (... rest of the output)

And checked the rate limit from Github, after a few times the rate limit is blocking me

root@pve:~# curl -i https://api.github.com/rate_limit

HTTP/2 200

access-control-allow-origin: *

access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset

cache-control: no-cache

content-security-policy: default-src 'none'

content-type: application/json; charset=utf-8

referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin

x-content-type-options: nosniff

x-frame-options: deny

x-github-media-type: github.v3; format=json

x-ratelimit-limit: 60

x-ratelimit-remaining: 0

x-ratelimit-reset: 1751787552

x-ratelimit-resource: core

x-ratelimit-used: 60

x-xss-protection: 1; mode=block

date: Sun, 06 Jul 2025 06:46:17 GMT

content-length: 714

x-github-request-id: DD50:38E22:8AC537E:8F2FFCF:686A1BB9



{

  "resources": {

    "core": {

      "limit": 60,

      "remaining": 0,

      "reset": 1751787552,

      "used": 60,

      "resource": "core"

    },

    "graphql": {

      "limit": 0,

      "remaining": 0,

      "reset": 1751787977,

      "used": 0,

      "resource": "graphql"

    },

    "integration_manifest": {

      "limit": 5000,

      "remaining": 5000,

      "reset": 1751787977,

      "used": 0,

      "resource": "integration_manifest"

    },

    "search": {

      "limit": 10,

      "remaining": 10,

      "reset": 1751784437,

      "used": 0,

      "resource": "search"

    }

  },

  "rate": {

    "limit": 60,

    "remaining": 0,

    "reset": 1751787552,

    "used": 60,

    "resource": "core"

  }

}

I honestly have no idea what else I could check to find the problem.

I'd greatly appreciate any hint on this.

[MickLesk]

You need to Check INSIDE the lxc, not on the host

[JorgeAnzola]

To check is I have access to Github? same result, 200 in the connection but throttled when I called the rate_limit

[MickLesk]

Yeah API Limit = waiting

[JorgeAnzola]

I know, but that’s the issue. If I wait, and the throttling is done, the problem persists.

[Ruvetuve]

I have the same issue @MickLesk. Via Gitea link it does not work either.. do we need to login to docker first?

   ✔️   IPv4 Internet Connected
   ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
curl: (22) The requested URL returned error: 403

[ERROR] in line 20: exit code 0: while executing command DOCKER_LATEST_VERSION=$(get_latest_release "moby/moby")

[ERROR] in line 1353: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/${var_install}.sh)"

I'm a fresh Proxmox user btw. Started today. I might be overlooking something

[MickLesk]

Ne thats the official docker Repo in gh (only for the Version crawling).

[tremor021]

I'm not really sure what you want @MickLesk to do with your network getting rate limited by github?

[Ruvetuve]

Not sure if the rate limit is the issue or if it's related to the script.

[tremor021]

its not script related, its your network.

[Ruvetuve]

Iam adding a github token to the curl request as a global header. This works when I test the limits:
curl -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/rate_limit

Trying to export this to curl:

printf 'header = "Authorization: Bearer %s"\n' "$GITHUB_TOKEN" > ~/.curlrc chmod 600 ~/.curlrc

Gives me a 401, debugging...

[Ruvetuve]

I just discovered that one of the containers on my NAS was sending requests to api.github.com every second. Disabling that container stopped the traffic. I’ll wait for the request limit to reset and then check again.

[Ruvetuve]

confirmed to be working as expected!