docs/translations/ru-RU/content/github/authenticating-to-github/using-ssh-over-the-https-port.md

title, intro, redirect_from, versions

title	intro	redirect_from	versions
Using SSH over the HTTPS port	Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/using-git/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.	/articles/using-ssh-over-the-https-port	free-pro-team *

{% tip %}

GitHub Enterprise users: Accessing GitHub Enterprise via SSH over the HTTPS port is currently not supported.

{% endtip %}

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

$ ssh -T -p 443 git@ssh.github.com
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
> provide shell access.

If that worked, great! If not, you may need to follow our troubleshooting guide.

Enabling SSH connections over HTTPS

If you are able to SSH into git@ssh.{{ site.data.variables.command_line.backticks }} over port 443, you can override your SSH settings to force any connection to {{ site.data.variables.product.product_location }} to run though that server and port.

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

Host {{ site.data.variables.command_line.codeblock }}
  Hostname ssh.{{ site.data.variables.command_line.codeblock }}
  Port 443

You can test that this works by connecting once more to {{ site.data.variables.product.product_location }}:

$ ssh -T git@{{ site.data.variables.command_line.codeblock }}
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
> provide shell access.