Help Wanted The requested URL returned error: 429

[fofware]

Hi guys
I get curl: (22) The requested URL returned error: 429 from any script I try

429: Too Many Requests
For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service).

I have a static IP v4 so I try from other location with other IP, same result

Any one, any Idea?

Thanks

[leosgarcia]

Hi guys,

This problem has also been happening to me every time I try to use any of the scripts.

It's been two days since I've been able to use any script.

Thanks.

[MickLesk]

And the Gitea Calls?

[fofware]

Gitea:

root@pve:~# bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/docker.sh)"

curl: (28) Failed to connect to git.community-scripts.org port 443 after 134750 ms: Could not connect to server
root@pve:~#

[MickLesk]

Then your complete server cannot Access to our repo and its Not only GitHub

[MickLesk]

Check your DNS, AdBlock or something. Curl 28 say your Network Timed Out in a simple curl call

[fofware]

Hi everyone, just wanted to share what I've tested so far:

The first thing I suspected was a network issue on my end, since I got the same result when trying to access the scripts via browser from different machines.

To rule that out, I asked a friend from a different location to try accessing the scripts—but we both use the same ISP—and he got the exact same response.

So it seems the issue might be related to the provider itself. I'm now planning to test access using a proxy or VPN to see if the ISP is the one blocking the connection. I'll report back once I have results from that test.

Also, I don't have any firewall, AdBlock, or similar tools that could interfere with the connection. I'm new to Proxmox, but I do have some networking experience.

Any ideas or suggestions are welcome. Thanks!

[fofware]

I ran traceroutes from both Linux and Windows environments to git.community-scripts.org and its hosting IP range. In both cases, the traffic successfully traverses Cogent's backbone and reaches the final ASN (as3330.net), which appears to be the hosting provider.

However, from that point onward, the trace either times out or loops indefinitely. This behavior suggests that the destination server or its upstream network is blocking ICMP traffic or has a misconfigured route. Importantly, this does not necessarily mean the server is down—it may simply be configured to ignore traceroute requests.

Given that packets reach Europe without loss or delay, this points to a routing or firewall issue closer to the destination, rather than a problem with my local setup or ISP.

If none of you are experiencing this issue, I'll keep looking for an alternative solution—because it doesn't seem like something I can fix on my side.

Thanks!

[MickLesk]

Just Ping from your Mobile Phone in your country? Or share your Network from Phone to your PC with Hotspot and try it? The Server is nearly 100% Uptime and reachable from several Networks all over the world.

And If you dont reach the GitHub Repo too (Not the Gitea Repo), all Look Like ISP Issues.

@michelroegl-brunner Look above.

[michelroegl-brunner]

That might be that our Provider dose not peer with your carrier, wich might be. There is not really anything i can do just now to be honest.
Edit:
Scratch that, you reach in the network of my provider, so no pearing issue. But your carrier might be on some sortof a Blacklist by Fortigate(my FW Vendor).
Try with a VPN with a austrian IP, and report if it works.

[fofware]

Thanks for the suggestion. I tested using an HTTP proxy with a US IP, and everything works perfectly — I can access both the Gitea repository and GitHub without any issues.

However, when I try proxies from other countries, including Austria, I still get errors when accessing both Gitea and GitHub. So far, only the US proxy provides full access.

Let me know if there's anything else I should try or test.

[fofware]

I did use Oxylabs like proxy