Failed to connect to github.com port 443 after 21124 ms: Couldn't connect to server

[marcolopes]

Select Topic Area

Question

Body

We are having connection issues with GIT, even using GitHub Desktop APP!

fatal: unable to access 'https://github.com/marcolopes/dma.git/': Failed to connect to github.com port 443 after 21124 ms: Couldn't connect to server

The connection using ECLIPSE SVN is SLOW SLOW SLOW, and hangs sometimes (when it doesen't hang, it will throw "org.apache.subversion.javahl.ClientException: Can't create session
svn: Unable to connect to a repository at URL 'https://github.com/marcolopes/dma/trunk/org.dma.eclipse'
Connection timed out
svn: Connection timed out"

Is there a problem with GIT?

We are used to it being slow using SVN, but this has nothing to do with it, since direct connection with GitHub Desktop (Windows) has the same problems...

Thanks!

[CMon]

we encounter the same on our machines, and its not restricted to a specific repo, commands that fail on the first run succeed on a second run. Not a solution for our build pipelines.

9:15:34 ~$ git ls-remote --tags --heads https://github.com/mgcrea/angular-strap.git
fatal: unable to access 'https://github.com/mgcrea/angular-strap.git/': Failed to connect to github.com port 443 after 129237 ms: Couldn't connect to server
9:17:45 ~$ git ls-remote --tags --heads https://github.com/mgcrea/angular-strap.git
005ca9c9fbb7651156139927ac38b29d850fb004        refs/heads/gh-pages
c024601dd8866181c3aab1567a05b68290840ef9        refs/heads/legacy
957bbf9841ff99f847d1f97153294f902e465b92        refs/heads/master
d8895dc39963cacf34ef084c6b8a58250c14802c        refs/tags/v0.5.10
81a830ec22d6f60ffb0413fafc85c1052d5531bd        refs/tags/v0.5.6
b6bdc373eea525c8a6fb77ef617288f67e56aff0        refs/tags/v0.5.7
...

[huelsmc]

Same issue here. Connections to github.com are failing sometimes. Another run often (not 100%) is successful.

[huelsmc]

In our case it's happening during a github workflow running on github runners but sometimes also own runners

[baizhu0414]

还真可以，离谱

[kpaaro]

I tried running curl https://github.com on our CI server and every 1/3 request hangs. The issue poped up when pulling from repos to start build pipelines. This behaviour was first noticed 24h ago in our CI server.

[kpaaro]

I also added a ticket in github support.

[marcolopes]

How can i do that? I tried and failed! :D

[kpaaro]

Which bit? support ticket? https://support.github.com

[jkralik]

I have also same issue with own runner:

Failed to connect to github.com port 443 after 130098 ms: Connection timed out

[hashbou]

Hello, we're having the same problem. It happens regularly and breaks our pipeline builds currently. We ruled out rate limiting and other network issues. It really seems to happen that the git servers at GitHub are not responsive from time to time.

We recognized this also since early yesterday.

Maybe this is related to: https://www.githubstatus.com/incidents/2gy2gddtv23d

[marcolopes]

Seems related... Started yesterday...

We are investigating reports of degraded performance for Git Operations
Posted 1 day ago. Sep 07, 2023 - 10:02 UTC

[AlexisFronteau]

Hi, we're having the same problem since yesterday and it is not resolved

[samwyndham]

We have also been experiencing issues since yesterday frequently resulting in failing GitHub action jobs. It is mainly manifesting itself as warning failing to download Actions, and errors using GitHub API over GitHubs CLI tool. I think it may relate to this issue: https://github.com/orgs/community/discussions/66444

[samwyndham]

I'm surprised that this issue is not yet visible on https://www.githubstatus.com/. I'm afraid that GitHub is not aware of it. Is there another way to alert GitHub?

[kpaaro]

For us the issue got reolved a few hour ago, and for the mean while I changed my hosts file to direct github.com to the US region load balancer.
The IP was provided in another thread about this issue.

[kpaaro]

[marcolopes]

Seems ok now... (yet a bit slower than usual)

[cdf1982]

Hello, in the last week I've also experienced frequent "Failed to connect to github.com port 443: Connection timed out" messages from different repositories; oddly enough, switching the IP address I connect from via VPN seems to solve. Are there issues with a too-aggressive DDOS prevention mechanism?

[kpaaro]

Last week et seemed more of a loadbalancing/dns issue, where one or more 'dead' ip's were still given out. And switching to the US ip solved the issue then. By now we have set everything back to normal.

[martin-coded]

I have this issue since today. Are there still problems?

[marcolopes]

All is fine here... (Slow, as usual, but no problems)

[martin-coded]

Thank you for confirmation! I just figured out, that a firewall was blocking the request for some unknown reason.

[marcolopes]

Problems are back... can't do anything!

GitHub Desktop Acess:
fatal: unable to access 'https://github.com/marcolopes/dma.git/': Failed to connect to github.com port 443 after 21246 ms: Couldn't connect to server

SVN Access:
org.apache.subversion.javahl.ClientException: Can't create session
svn: Commit failed (details follow):
svn: Unable to connect to a repository at URL
Connection timed out
svn: Connection timed out

[xingshengao]

Close fireWall software, and sloved.

[Peter-Pan010612]

you can try restart it

[Adrian1jr]

I solved my problem by using a USB device to get Wifi on my pc and connecting to “other” wifi, basically the same network but in wifi mode lol

[leekinm]

Actually, closing firewall works well, but if i keep truning the firewall off whether my computer will be attacked or not? Is there any permant solution?

[studyingforever1]

yes i solve my problem by closing firewall too thanks . by the way, the guy upstrair, you can close your firewall after push your code.

[journey0616]

you can try restart it

nice! restart computer perfectly to solve my problem

[staramidst]

I just made an ssh key with ssh-keygen put the key in the folder I made and used it to add my key and then tested it with git clone ssh the repo copy and paste.

[Stephanommg]

This worked for me

[ZupoLlask]

A few months ago, while certain operations (like git clone) still were working fine, some others (like git checkout) started to behave as described by you guys.

I've just find out that the culprit was using the URL with ".git" suffix (e.g., https://github.com/marcolopes/dma.git instead of simply https://github.com/marcolopes/dma).

As soon as I removed that ".git" suffix from my URLs, all the trouble went away.

[marcolopes]

Thanks! This does not matter anymore because GIT has dropped SVN support... (and the problems were related to SVN use)

[chithambaramoorthii]

Same issue here from (India)

[ghost]

you find solution of these issue

[xEverth]

Action failed because of this during auto-commit step

[Danthesage01]

Just experienced this issue now (Nigeria)

[dev-zeb]

Same issue here, facing since this morning. (Bangladesh)
However, when I use mobile data using Hotspot the issue doesn't occur. It's occurring only when I'm connected to the Wi-Fi.

[Ardiannn08]

same issue here from (Indonesia) since last 3 days

[shadan1234]

I have found the solution to the problem !!! . Just switch your wifi , then run the same git cmds , and it will work.

[lincolncesardev]

there was a vs.code folder containing a file called .settings . there was a port on default. Deleted and the clone was ok here

[jenniebxiao]

same issue here
Failed to connect to github.com port 443 after 21045 ms: Couldn't connect to server

I changed my network, and issue fixed

[LeftoverAtoms]

`git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128.
stderr:
fatal: unable to access 'repository': Failed to connect to github.com port 443 after 21107 ms: Couldn't connect to server

Had the same issue, toggling Wifi off/on solved the issue.

[chanmaoganda]

Same issue, toggling Wifi works!

[PiyushBagde]

i am experiencing the same, does anyone know how to fix this?

fatal: unable to access (repo link) ': 
Failed to connect to github.com port 443 after 21168 ms: Couldn't connect to server

[PiyushBagde]

Hi, I'm curious if this helps you: https://github.com/orgs/community/discussions/29269#discussioncomment-10094288

Thanks

[viethung0823]

try to do it multiple times works but it's so annoy when we do not know the root caused

[chanmaoganda]

perhaps set your dns server to google server?(8.8.8.8)

[PiyushBagde]

try to do it multiple times works but it's so annoy when we do not know the root cause

Turn off private DNS if you using one

[viethung0823]

try to do it multiple times works but it's so annoy when we do not know the root cause

Turn off private DNS if you using one

I've had checked network settings, no dns, no firewall, or VPN was on.

[gertcuykens]

Same issue. ipv6 related maybe ? I don't have ipv4 address

[PalashCoder]

Same issue I've faced.
This issue can be occurred when you previously pulled from the same repo and forget to run "npm i" this will install the dependencies according to the package.json and after running npm i, you can push your code without any problem.

[upsampling]

Same issue here in Mexico.

curl: (28) Failed to connect to github.com port 443 after 138319 ms: Couldn't connect to server

[TerenceTian625]

Are you using aws ec2 instance as a self-hosted runner, I'm facing the same error as yours when spinning up ec2 instance as self-hosted runner. Sometime it worked but sometimes it failed.

[franklizh]

here my steps to solve this problem:
find your computer internet setting ,find proxy,address,port
then input code in git bash:

git config --global http.proxy http://127.0.0.1:your port num
git config --global https.proxy http://127.0.0.1:your port num

[Morning-Ye]

This works for me, thanks!

[franklizh]

here my steps to solve this problem:
find your computer internet setting ,find proxy,address,port
then input code in git bash:

git config --global http.proxy http://127.0.0.1:your port num
git config --global https.proxy http://127.0.0.1:your port num

[LiangMouse]

I resolved it by toggling Wifi off/on.

[JustCod101]

I think i have a good solution for you , JUST turn on TUN MODE in your proxy software