git ssh 22 port is not available when you configure Git ssh via HTTPS 443 port

Using SSH over the HTTPS port

Sometimes, firewalls refuse to allow SSH connections entirely. If using HTTPS cloning with credential caching are not a option, you can attempt to clone using an SSH connection made Ove R the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.

GitHub Enterprise Users:accessing GitHub Enterprise via SSH over the HTTPS port was currently not supported.

To test if SSH over the HTTPS port is possible, run this SSH command:

SSH-T-P 443 [email protected]username! You've successfully authenticated, but GitHub does notprovide shell access.

If that worked, great! If not, the need to follow we troubleshooting guide.

Enabling SSH connections over HTTPS

If you [email protected] is able to ssh in over port 443, you can override the your SSH settings to force any connection to GitHub to R Un though that server and port.

To set of this in your SSH config, edit the file ~/.ssh/config at, and add this section:

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

Can test that the this works by connecting once more to GitHub:

ssh-t [email protected]username! You've successfully authenticated, but GitHub does notprovide shell access.

Original address: https://help.github.com/articles/using-ssh-over-the-https-port/

git ssh 22 port is not available when you configure Git ssh via HTTPS 443 port