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>
59 lines
2.3 KiB
Markdown
59 lines
2.3 KiB
Markdown
---
|
|
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: '*'
|
|
github-ae: '*'
|
|
topics:
|
|
- ssh
|
|
---
|
|
|
|
When running remote Git commands or SSH, your connection might time out:
|
|
|
|
```shell
|
|
$ ssh -vT git@{% data variables.command_line.codeblock %}
|
|
> OpenSSH_8.1p1, LibreSSL 2.7.3
|
|
> debug1: Connecting to {% 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 {% data variables.command_line.codeblock %} port 22: Connection timed out
|
|
> ssh: connect to host {% 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](/github/getting-started-with-github/about-remote-repositories) you're using:
|
|
|
|
```shell
|
|
$ git clone https://{% 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 {% 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 {% 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 %}
|