885da5b3d3
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * fix malformed liquid * add next directory to exclude list * currentversion -> currentVersion * fix liquid errors * fix liquid errors * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on * Reset known broken translation files LAST * Run script/i18n/homogenize-frontmatter.js Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
48 lines
1.8 KiB
Markdown
48 lines
1.8 KiB
Markdown
---
|
|
title: Using SSH over the HTTPS port
|
|
intro: '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.'
|
|
redirect_from:
|
|
- /articles/using-ssh-over-the-https-port
|
|
versions:
|
|
free-pro-team: '*'
|
|
topics:
|
|
- SSH
|
|
---
|
|
|
|
{% tip %}
|
|
|
|
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} 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:
|
|
|
|
```shell
|
|
$ 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](/articles/error-permission-denied-publickey).
|
|
|
|
### 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 %}:
|
|
|
|
```shell
|
|
$ ssh -T git@{% data variables.command_line.codeblock %}
|
|
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
|
|
> provide shell access.
|
|
```
|