When you see this warning, you can enter yes. The authenticity of host ' (104.192.143.1)' can't be established. If the host is not in your ~/.ssh/known_hosts file, SSH warns you that it's adding the Bitbucket host to known hosts if you continue: The authenticity of host ' (104.192.143.1)' can't be established.īecause Bitbucket hosts only allow Git to make SSH connections, the first time you access Bitbucket using the SSH URL, your SSH client checks to see if the Bitbucket host is a known host. Talk to your network administrator to resolve the issue. Ssh: connect to host port 22: Operation timed outįatal: The remote end hung up unexpectedlyĪ timeout means that your computer was unable to reach Bitbucket, likely due to something in your own network. For example, your network administrator may have a firewall rule that blocks the connection. bashrc doesn't launch correctly, you may see these types of messages: Then, continue using the ssh-add command to add your keys. To start the agent, run the following: macOS/Linux Most likely your ssh-agent did not start properly. You may see this error when trying to use the ssh-add command. Could not open a connection to your authentication agent If you don't see your SSH key, click Add Key. If you don't see your key listed, add it by entering ssh-add followed by the path to the private key file:ĭouble-click the Pageant (PuTTY Authentication Agent) icon in your system tray to open the Pageant Key List dialog. To find out what keys your SSH agent is currently offering and to add them to the agent: You may run into this issue if you've recently restarted your system. If your SSH agent doesn't know to offer Bitbucket a key, the connection fails. Your key isn't loaded into your SSH agent If you don't have any keys listed, you can follow our Set up an SSH key documentation to set one up. The SSH keys page shows a list of any existing keys. To check if your public key is loaded into Bitbucket, do the following:įrom Bitbucket, choose Personal settings from your avatar in the lower left. Your public key isn't loaded into Bitbucket You shouldn't use sudo when cloning, pushing, or pulling because the ssh-agent runs on the user level, not the root level. You used sudo when attempting the connection Here are the most common reasons why you may see these messages: When attempting to clone, push, or pull over SSH with Git, you may receive one of these messages if Bitbucket couldn't authenticate with the keys that your SSH agent offered. You may see the following error messages when trying to authenticate over SSH. From a repository in Sourcetree, you can find the command line by clicking Terminal in the top right. However, you may need to using the command line for others. If you're using Sourcetree, some of these solutions come with Sourcetree steps. # ASNumber: 15169 ASName: GOOGLE ASHandle: AS15169 RegDate: Updated: Ref: OrgName: Google LLC OrgId: GOGL Address: 1600 Amphitheatre Parkway City: Mountain View StateProv: CA PostalCode: 94043 Country: US RegDate: Updated: Ref: OrgAbuseHandle: ABUSE5250-ARIN OrgAbuseName: Abuse OrgAbusePhone: +1-65 OrgAbuseEmail: OrgAbuseRef: OrgTechHandle: ZG39-ARIN OrgTechName: Google LLC OrgTechPhone: +1-65 OrgTechEmail: OrgTechRef: RTechHandle: ZG39-ARIN RTechName: Google LLC RTechPhone: +1-65 RTechEmail: RTechRef: # ARIN WHOIS data and services are subject to the Terms of Use # available at: # If you see inaccuracies in the results, please report at # Copyright 1997-2018, American Registry for Internet Numbers, Ltd.If you're having problems with SSH, here are some things you can try when troubleshooting your issues. # ARIN WHOIS data and services are subject to the Terms of Use # available at: # If you see inaccuracies in the results, please report at # Copyright 1997-2018, American Registry for Internet Numbers, Ltd.