git pull error: ERROR: no healthy upstream fatal: Could not read from remote repository.

[davxiao]

Select Topic Area

Question

Body

SSH access git pull stopped working for a few hours now.
Typical error message I'm getting:

ERROR: no healthy upstream
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

[colin-oos]

Same issue for me. I spent like an hour troubleshooting my ssh connection/key and even generated a whole new one before I noticed that GitHub's ssh and https is down.

[wimglenn]

Oddly enough ssh -T git@github.com works fine, but can't push/pull.

[Kaosar3662]

The same happened to my colleague once
here are all the points that can help you.

1. Check if the Git host (GitHub, GitLab, etc.) is having an outage.
2. Make sure your internet or DNS isn’t blocking the SSH address.
3. Try switching to HTTPS to confirm if SSH is the only thing failing.
4. Verify your SSH key is still valid and hasn’t been removed from your account.
5. If you’re using a self-hosted Git server, restart the proxy or Git service because the backend may be down.

[nxndi]

Hi davxiao,
Thanks for sharing the issue you're experiencing.

from the error i see, usually indicates a temporary problem on the hosting side (GitHub’s SSH service or network routing) rather than an issue with your local SSH configuration.

Here are a few things you can try while waiting for the service to return to normal:

1. Check GitHub Status
   Visit the GitHub Status page to see if there are ongoing incidents affecting SSH or repository access.

2. Test your SSH connection
   Run: ssh -T git@github.com

3. Try switching networks or using VPN
   Sometimes routing issues in specific ISPs can cause this error.

4. Use HTTPS as a temporary fallback
   You can temporarily switch to HTTPS to continue pulling/pushing:
   git remote set-url origin https://github.com/USERNAME/REPO.git

Since the issue started only a few hours ago and the error mentions "no healthy upstream", it is likely a temporary service instability. If the problem persists for much longer, you may consider opening a support ticket with GitHub.

Hope this helps, and let me know if you need help testing your SSH setup.

[davxiao]

Thanks to all who cared to spend time commenting in this thread.
It appears that the problem was with the remote host (github) and not with the local SSH configuration.
It is resolved by now.