Hello git history spelunker!

Are you looking for something? Here is all of the GitHub Docs history in one single commit. Enjoy! 🎉

content/github/authenticating-to-github/error-bad-file-number.md

@@ -0,0 +1,55 @@
+---
+title: 'Error: Bad file number'
+intro: This error usually means you were unable to connect to the server. Often this is caused by firewalls and proxy servers.
+redirect_from:
+  - /articles/error-bad-file-number
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+---
+
+When running remote Git commands or SSH, your connection might time out:
+
+```shell
+$ ssh -vT git@{{ site.data.variables.command_line.codeblock }}
+> OpenSSH_5.8p1, OpenSSL 1.0.0d 8 Feb 2011
+> debug1: Connecting to {{ site.data.variables.command_line.codeblock }} [207.97.227.239] port 22.
+> debug1: connect to address 207.97.227.239 port 22: Connection timed out
+> ssh: connect to host {{ site.data.variables.command_line.codeblock }} port 22: Connection timed out
+> ssh: connect to host {{ site.data.variables.command_line.codeblock }} port 22: Bad file number
+```
+
+### Solving the issue
+
+#### Use HTTPS
+
+Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/articles/which-remote-url-should-i-use) you're using:
+
+```shell
+$ git clone https://{{ site.data.variables.command_line.codeblock }}/<em>username</em>/<em>reponame</em>.git
+> Cloning into 'reponame'...
+> remote: Counting objects: 84, done.
+> remote: Compressing objects: 100% (45/45), done.
+> remote: Total 84 (delta 43), reused 78 (delta 37)
+> Unpacking objects: 100% (84/84), done.
+```
+
+#### Test from a different network
+
+If you can connect the computer to another network that doesn't have a firewall, you can try testing your SSH connection to {{ site.data.variables.product.product_name }}. If everything works as it should, contact your network administrator for help on changing the firewall settings to allow your SSH connection to {{ site.data.variables.product.product_name }} to succeed.
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+#### Using SSH over the HTTPS port
+
+If using HTTPS is not an option, and your firewall admin refuses to allow SSH connections, you can try using [SSH over the HTTPS port](/articles/using-ssh-over-the-https-port) instead.
+
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+### Further reading
+
+- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
+
+{% endif %}