I cannot update my ip is blocked by github

ℹ️ Support
, , ,
1

The Basics

  • Nextcloud Server version: 33.0.0

  • Operating system and version: Debian 12

  • Web server and version: Apache 2.4

  • PHP version: 8.3

  • Is this the first time you’ve seen this error? No

  • When did this problem seem to first start? 3 months ago

  • Installation method: Bare Metal/Archive

  • Are you using Cloudflare, mod_security, or similar? No

Summary:

My dedicated OVH server (France) cannot connect to github.com port 443 — blocked on GitHub’s side, not mine. All other HTTPS sites work fine. github.com wants me to subscribe to their service to unlock my IP…

This causes two problems:

  1. Core updater times out trying GitHub before attempting download.nextcloud.com

  2. occ app:update fails silently because app archives are hosted on GitHub with no fallback

I patched getDownloadURLs() in updater.phar and index.php using array_reverse() to fix issue #1, but issue #2 remains unsolved.

Feature request: Could Nextcloud either:

  • Add a config.php option to specify a preferred download mirror

  • Add a fallback mechanism in downloadApp() in lib/private/Installer.php

  • Host app archives on download.nextcloud.com instead of GitHub

Log entry:

Curl error: Failed to connect to github.com port 443 after 130496 ms
2

What is the source of this statement? Are you sure, or is that just a guess?

I know that GitHub imposes rate limits on API requests (and possibly other operations) if too many requests are made from a single IP. In that case, however, you’ll receive an HTTP response stating this. In your case, however, GitHub appears to be completely unreachable:

Please post the output of the following commands:

dig github.com
traceroute github.com
curl -Iv https://github.com
3

At the moment, GitHub is experiencing the following outage, which is still ongoing as I write this. You might just have to wait and test again after the outage is resolved :slight_smile:

We are investigating reports of impacted performance for some GitHub services.

https://www.githubstatus.com/incidents/dbypmw7h77l5

But I’m not sure if that applies to downloads as well.

4

I got a refusal form github asking to subscribe to open a ticket asking to unban (that I guess) my IP.

5

My problem occur for several month, it is not new. I had to do the last Nextcloud update by command line. This time I just want to update the applications and I have the same problem.

6

; <<>> DiG 9.18.41-1~deb12u1-Debian <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44216
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;github.com. IN A

;; ANSWER SECTION:
github.com. 47 IN A 140.82.121.4

;; Query time: 0 msec
;; SERVER: 213.186.33.99#53(213.186.33.99) (UDP)
;; WHEN: Tue Apr 28 17:15:44 CEST 2026
;; MSG SIZE rcvd: 55

traceroute github.com
traceroute to github.com (140.82.121.3), 30 hops max, 60 byte packets
1 51.178.79.252 (51.178.79.252) 0.483 ms 0.498 ms 0.558 ms
2 10.162.66.202 (10.162.66.202) 0.335 ms 0.347 ms 10.162.66.204 (10.162.66.204) 0.581 ms
3 10.17.151.78 (10.17.151.78) 0.596 ms 10.17.151.64 (10.17.151.64) 0.414 ms 10.17.151.66 (10.17.151.66) 0.565 ms
4 10.73.240.66 (10.73.240.66) 0.256 ms 10.73.240.64 (10.73.240.64) 0.288 ms 10.73.240.67 (10.73.240.67) 0.369 ms
5 172.20.16.32 (172.20.16.32) 3.531 ms 172.20.16.48 (172.20.16.48) 1.983 ms 172.20.16.32 (172.20.16.32) 3.498 ms
6 37.59.16.29 (37.59.16.29) 1.093 ms 1.109 ms 37.59.16.31 (37.59.16.31) 0.467 ms
7 fra-fr5-sbb1-nc5.de.eu (213.186.32.213) 8.712 ms 8.720 ms be104.fra-fra15-sbb2-8k.de.eu (91.121.131.19) 11.307 ms
8 10.200.6.199 (10.200.6.199) 10.924 ms 10.200.0.13 (10.200.0.13) 10.301 ms 10.310 ms
9 de-cix.fra.github.com (80.81.196.79) 11.962 ms de-cix2.fra.github.com (80.81.196.80) 9.216 ms de-cix.fra.github.com (80.81.196.79) 11.800 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

curl -Iv https://github.com

  • Trying 140.82.121.3:443…
  • connect to 140.82.121.3 port 443 failed: Connexion terminée par expiration du délai d’attente
  • Failed to connect to github.com port 443 after 129951 ms: Couldn’t connect to server
  • Closing connection 0
    curl: (28) Failed to connect to github.com port 443 after 129951 ms: Couldn’t connect to server
7

I’ve never heard of GitHub blocking IPs (in the sense that a connection can’t be established). There’s no mention of this here either, even though it would make sense there:

That’s why I’m a bit sceptical. But yes, you might still be right. I don’t known :slight_smile:

  • Your Dig looks good
  • Your traceroute looks also good

Since it’s about networking, you could try asking noc@github.com or OVH (your hoster). But I’m not sure if that’ll help. Do other curl requests to, for example, curl -I https://google.com work? Do you see anything in your server’s syslog whilst you’re running the curl command to GitHub? Which firewall (e.g. Nftables, Iptables, etc.) do you have enabled?

8

Thank you :blue_heart: for your time, your suggestion helped me to find the problem, the ip was blocked by ipset ! I thought of fail2ban but forgot ipset.