diff --git a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
index 9f094aa659..92f37fba9d 100644
--- a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -26,8 +26,20 @@ $ ssh -T -p 443 git@ssh.github.com
 > provide shell access.
 ```
 
+{% note %}
+
+**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
+
+{% endnote %} 
+
 If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
 
+Now, to clone the repository, you can run the following command:
+
+```
+$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
+```
+
 ## 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.location.product_location %} to run through that server and port.
@@ -48,3 +60,19 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > Hi USERNAME! You've successfully authenticated, but GitHub does not
 > provide shell access.
 ```
+
+## Updating known hosts
+
+The first time you interact with GitHub after switching to port 443, you may get a warning message
+that the host wasn't found in `known_hosts`, or that it was found by another name.
+
+```ShellSession
+> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
+> ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
+> This host key is known by the following other names/addresses:
+>     ~/.ssh/known_hosts:32: github.com
+> Are you sure you want to continue connecting (yes/no/[fingerprint])? 
+```
+
+It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches
+one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
diff --git a/content/get-started/using-github/troubleshooting-connectivity-problems.md b/content/get-started/using-github/troubleshooting-connectivity-problems.md
index 948f1bc805..bdd31c3320 100644
--- a/content/get-started/using-github/troubleshooting-connectivity-problems.md
+++ b/content/get-started/using-github/troubleshooting-connectivity-problems.md
@@ -32,6 +32,8 @@ If you're unable to verify with the captcha:
 
 Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve connectivity. For more information, see "[Troubleshooting cloning errors](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)."
 
+If you prefer to use SSH but the port is blocked, you can use an alternative port. For more information, see "[Using SSH over the HTTPS port](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port)".
+
 If you're encountering timeouts with SSH, see "[Error: Bad file number](/articles/error-bad-file-number)."
 
 ## Troubleshooting slow downloads and intermittent slow connections