d27e09cc5b
* backticks for javascript * Update sorting-search-results.md backticks asc * Update installing-github-enterprise-server-on-azure.md fixed vm az * Update searching-for-repositories.md backticks * Update searching-code.md backticks * Update searching-issues-and-pull-requests.md backticks * Update searching-issues-and-pull-requests.md * Update understanding-the-search-syntax.md * Update searching-for-packages.md * Update upgrading-from-dependabotcom-to-github-native-dependabot.md * fix errors in source * removed spaces * vale docs * link to md link * spacing for backticks * docs draft * remove space * removed spacing * drafting * drafting * draft * escape single quote * escape another single quote * fix broken link * vale guide * edge case * edge case ex * edge case ex link * grammer * grammer * Update vale-guide.md clarity * Update vale-guide.md small edit * clarity * sentence fix * Rubocop to RuboCop * Rubocop -> RuboCop * terms in backticks * pem in backtick * idp -> IdP * file names in backticks * public/private rsa in backticks * fix vale errors * fix vale errors * Update sending-enterprise-contributions-to-your-githubcom-profile.md fix dot-com links * Update metadata-syntax-for-github-actions.md * Update configuring-codeql-cli-in-your-ci-system.md * Update content/get-started/getting-started-with-git/associating-text-editors-with-git.md Co-authored-by: Vanessa <vgrl@github.com> * Update managing-deploy-keys.md public and private rsa key pair * Update libraries.md removed backticks for consistency * Update sorting-search-results.md removed backticks for consistency * Update metadata-syntax-for-github-actions.md removed backticks for consistency * Update metadata-syntax-for-github-actions.md removed backticks * delete vale config files Co-authored-by: Vanessa <vgrl@github.com> Co-authored-by: Amy Burns <timeyoutakeit@github.com>
2.0 KiB
title, intro, redirect_from, versions, topics, shortTitle
| title | intro | redirect_from | versions | topics | shortTitle | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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. |
|
|
|
Use SSH over HTTPS port |
{% 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:
$ 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 through that server and port.
To set this in your SSH confifguration file, 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.