How to fix ssh: connect to host github.com port 22: Connection timed out (firewall) in Git

First, confirm that the issue is specifically a firewall blocking port 22:

# Test standard SSH connection
ssh -vT [email protected]

If blocked by a firewall, you'll see the connection attempt hang and eventually fail with "Connection timed out". The verbose output (-v) will show it stuck at "Connecting to github.com port 22".

To confirm HTTPS works (proving it's a port issue, not general connectivity):

curl -I https://github.com

If HTTPS works but SSH doesn't, a firewall is almost certainly blocking port 22.

GitHub provides SSH access on port 443, which firewalls typically allow. Test if this works:

ssh -T -p 443 [email protected]

Expected successful output:

Hi username! You've successfully authenticated, but GitHub does not provide shell access.

If this works, proceed to make this configuration permanent. Note that the hostname is ssh.github.com, not github.com - GitHub runs a separate SSH server for port 443 connections.

Add a permanent SSH configuration to route all GitHub connections through port 443:

# Create .ssh directory if it doesn't exist
mkdir -p ~/.ssh

# Create or edit the SSH config file
nano ~/.ssh/config

Add this configuration:

Host github.com
    Hostname ssh.github.com
    Port 443
    User git

Set proper permissions and test:

chmod 600 ~/.ssh/config
ssh -T [email protected]

Your Git commands will now automatically use port 443 without changing any remote URLs.

If you prefer not to modify SSH config, configure Git to rewrite URLs globally:

git config --global url."ssh://[email protected]:443/".insteadOf "[email protected]:"

This automatically converts SSH URLs to use port 443. Verify the configuration:

git config --global --get-regexp url

To remove this configuration later:

git config --global --unset url."ssh://[email protected]:443/".insteadOf

If SSH on port 443 is also blocked, switch to HTTPS authentication:

# Check current remote
git remote -v

# Change to HTTPS URL
git remote set-url origin https://github.com/username/repository.git

For authentication, create a Personal Access Token (PAT):
1. Go to GitHub Settings > Developer settings > Personal access tokens
2. Generate a new token with 'repo' scope
3. Use the token as your password when prompted

To avoid entering credentials repeatedly:

# Cache credentials for 1 hour
git config --global credential.helper 'cache --timeout=3600'

# Or store permanently (less secure)
git config --global credential.helper store

Your local firewall might also be blocking SSH. Add exceptions if needed:

Windows Defender Firewall:
1. Open Windows Security > Firewall & network protection
2. Click "Allow an app through firewall"
3. Add your SSH client (Git Bash, OpenSSH) for outbound connections

Linux (UFW):

# Allow outbound SSH
sudo ufw allow out 22/tcp
sudo ufw allow out 443/tcp

# Verify rules
sudo ufw status

macOS:

# Check firewall status
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate

# Add SSH exception if needed
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/bin/ssh

If you're in a corporate environment, consider requesting a firewall exception:

1. Document the business need for SSH access to GitHub
2. Request that IT either:
- Allow outbound connections to github.com on port 22
- Whitelist SSH traffic to GitHub's IP ranges
- Allow port 443 to ssh.github.com

GitHub's IP ranges are published at: https://api.github.com/meta

For many organizations, explaining that port 443 SSH is a secure alternative that doesn't require opening port 22 can help get approval more easily.