5a20716c7e
* Rename map topic * Delete map topic * Rename map topic * Add redirect * Remove last two map topics * Move article on adding a remote into a long-form guide * Move article on changing a remote's URL * Move articles on renaming and removing remotes * Move remote URL article * Fix typo * Remove category index file * Move a few articles to the new category * Move a few more files * Move managing remote repos article * Move the rest of the getting started with git map topic * Move the first half of the using git map topic * Move the rest of the articles and 🔥 the directory * Fix failing test * Remove Using Git from product index * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com> * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com>
1.8 KiB
1.8 KiB
title, intro, redirect_from, versions, topics
| title | intro | redirect_from | versions | topics | ||||
|---|---|---|---|---|---|---|---|---|
| Using SSH over the HTTPS port | Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/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. |
|
|
|
{% 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.{% data variables.command_line.backticks %} over port 443, you can override your SSH settings to force any connection to {% 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 {% data variables.command_line.codeblock %}
Hostname ssh.{% data variables.command_line.codeblock %}
Port 443
User git
You can test that this works by connecting once more to {% data variables.product.product_location %}:
$ ssh -T git@{% data variables.command_line.codeblock %}
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
> provide shell access.