Recommended Free Tools
If GitHub is blocked while you need to push, first identify what is failing: network access, SSH authentication, repository permissions, or an organizational access rule. If only SSH is blocked and your network permits Git over HTTPS, change the repository’s remote to its HTTPS address and authenticate with a method GitHub accepts. If you need SSH and port 22 is blocked, GitHub documents an SSH connection through ssh.github.com on port 443—but proxies and organization policies can still block it.
Identify what “blocked” means
GitHub connection failures can have different causes, and changing protocols will not fix every one. GitHub Docs says firewalls, proxy servers, corporate networks, and other network settings commonly cause connection problems. Use the error message and the protocol in your remote URL to choose the next step.
As an Amazon Associate I earn from qualifying purchases.
- SSH timeout or connection failure: If Git is trying to reach
github.comon port 22 and the connection times out, the network may be blocking SSH traffic. HTTPS or SSH over port 443 may be options if the network and its administrator permit them. Permission denied (publickey): This points to SSH authentication, not by itself to a firewall block. Check that the connection uses the SSH usergit, that an SSH key is being offered, and that the key’s public half is attached to the GitHub account you intend to use. You also need write permission on the repository.- HTTPS is blocked or an organization restriction appears: A proxy or account policy may be limiting access. Enterprise Cloud administrators can configure a corporate proxy that restricts authentication by account. Ask the administrator which access route and account are approved.
- TLS certificate error: GitHub’s SSH troubleshooting guidance notes that an outdated CA root certificate can prevent pushes and pulls. Follow the certificate-error path rather than treating it as a port problem.
Check the remote protocol with git remote -v. A remote beginning with [email protected]: or ssh:// uses SSH; one beginning with https:// uses HTTPS.
Option 1: Switch the remote to HTTPS
If SSH is blocked but HTTPS Git traffic is permitted, changing the remote is often the simplest fallback for a port-22 connection problem. This changes Git’s transport; it does not grant repository access, supply authentication, or override an organization’s policy.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
- Run
git remote -vin the repository to check the remote name and current URL. The usual remote name isorigin. - Set that remote to the repository’s HTTPS URL:
git remote set-url origin https://github.com/OWNER/REPOSITORY.git. ReplaceOWNERandREPOSITORYwith the repository’s actual owner and name. If your remote has another name, use that name instead oforigin. - Run
git remote -vagain and confirm the remote now shows the HTTPS address. - Retry your push. Complete authentication using a method GitHub accepts, and make sure your account has write permission for the repository.
Do not put a password or token in the remote URL. If HTTPS authentication is rejected, resolve that authentication or account-access issue rather than repeatedly changing the URL.
Option 2: Test SSH through port 443
GitHub’s documented SSH-over-443 endpoint is ssh.github.com, not github.com. First test whether you can reach and authenticate to that endpoint:
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
ssh -T -p 443 [email protected]A successful test may display: Hi USERNAME! You've successfully authenticated, but GitHub does not provide shell access. This confirms SSH authentication, not permission to push to a particular repository.
Configure Git to use the endpoint for GitHub SSH remotes
If the test succeeds and the route is allowed, add this entry to your SSH configuration file, usually ~/.ssh/config:
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Host github.com
Hostname ssh.github.com
Port 443
User gitWith this entry, SSH connections addressed to github.com use ssh.github.com on port 443. An alternative for a one-off clone is ssh://[email protected]:443/OWNER/REPOSITORY.git, with the actual repository owner and name in place of those words.
Verify the host key instead of bypassing the warning
On first use, SSH may report that the host is not yet in known_hosts, or that it is known under another name. Compare the presented host-key fingerprint with GitHub’s published fingerprints before accepting it. Do not disable host-key checking to get past the warning.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Know when port 443 will not help
GitHub says most firewall rules should allow SSH on the HTTPS port, but proxy servers may interfere. SSH over port 443 is unsupported for GitHub Enterprise Server and GitHub Enterprise Cloud with data residency. Do not assume GitHub.com hostnames or this configuration apply to a self-hosted Enterprise Server deployment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When the network belongs to your workplace or school
A different network can help diagnose whether the problem is specific to a managed network, but it is not authorization to work around that network’s rules. GitHub recommends checking whether network rules block the traffic and asking the network administrator to allow the required access.
Best Value
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
- If a restriction is accidental, the administrator can identify the needed allow-list or proxy change.
- If access is intentionally restricted, request an approved route or account and follow the organization’s policy. An alternate port is not automatically an authorized bypass.
- Enterprise Cloud’s corporate-proxy controls apply to supported HTTP(S) requests; Git SSH is handled separately, and administrators can block SSH endpoints or ports.
Choose a route based on the failure and the policy
| Situation | Next step | What it does not solve |
|---|---|---|
| SSH to port 22 times out; HTTPS Git is allowed | Change the remote to HTTPS and authenticate with an accepted method. | It does not grant repository write access or override network policy. |
| SSH to port 22 times out; SSH is needed and port 443 is permitted | Test ssh.github.com on port 443, then configure SSH if the test succeeds. |
It may still fail through a proxy, and it is unsupported for the Enterprise variants noted above. |
Permission denied (publickey) |
Check the SSH user, offered key, account association, and repository write permission. | Changing ports alone does not fix a missing or unrecognized key. |
| HTTPS or SSH is restricted by an organization | Ask the network or GitHub organization administrator for an approved route and account. | A transport change does not authorize access that policy denies. |
| TLS certificate error | Investigate the certificate and CA-root issue. | Switching SSH ports is not a certificate repair. |
The right choice depends on which traffic the network allows, how your account authenticates, which GitHub deployment you use, and whether the administrator authorizes the route.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
