# Can't SSH into Build Machine

**URL:** <https://discuss.circleci.com/t/cant-ssh-into-build-machine/558>\
**Category:** Build Environment\
**Created:** [November 16, 2015, 9:32pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558 "2015-11-16T21:32:47Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 9:32pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/1 "2015-11-16T21:32:47Z")

</div>

I am trying to debug my Circle build and would like to SSH into the build, but have been unable to do so. I’ve followed the documentation on the website at [https://circleci.com/docs/ssh-build/](https://circleci.com/docs/ssh-build/), and all the queries come back as expected. It appears to be trying to SSH into Github and to the CircleCI build with the same public key, but I’m unable to successfully log into Circle CI.

Any help would be appreciated.

Thanks.

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [November 16, 2015, 9:34pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/2 "2015-11-16T21:34:19Z")

</div>

Could you try to SSH with verbose logging and paste the output here?

`ssh -vvv -p $PORT ubuntu@$IPADDRESS`

Best,  
Lev

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 9:54pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/3 "2015-11-16T21:54:42Z")

</div>

![](https://global.discourse-cdn.com/circleci/original/1X/321a31cf05e92015960ca9813a84ddaad0cab706.png)

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 9:55pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/4 "2015-11-16T21:55:14Z")

</div>

![](https://global.discourse-cdn.com/circleci/original/1X/23e8317c82763b1385f0c9b0e1bb1cf881b55fbe.png)

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 9:56pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/5 "2015-11-16T21:56:33Z")

</div>

I don’t know how to post plain text here without it saying “New Users can’t mention more than 2 users” in a post. I can paste the plain text, but please let me know how to not mention people.

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [November 16, 2015, 9:58pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/6 "2015-11-16T21:58:06Z")

</div>

Where are you running this from, it looks like another AWS box?

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 10:02pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/7 "2015-11-16T22:02:38Z")

</div>

Yea, I’m running from another AWS box (I do all my work on an AWS RI instance)

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [November 16, 2015, 10:03pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/8 "2015-11-16T22:03:43Z")

</div>

Is the public key of that box on GitHub?

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 16, 2015, 10:24pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/9 "2015-11-16T22:24:44Z")

</div>

Which key are you referring to? Do you mean the key that we use to boot up AWS machines? We have the private key for that but we don’t have it on Git. We have another key on Git that allows us to access our code in Git. We do have that key loaded on our machines.

But if you’re referring to the public key of my personal RI, it is not on Github.

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [November 16, 2015, 11:37pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/10 "2015-11-16T23:37:57Z")

</div>

> [@justinsixty](#):
>
> But if you’re referring to the public key of my personal RI,

Yes, this key needs to be on GitHub. Alternatively if you have a key from your local computer that you are connecting to the AWS instance with on GitHub you should be able to connect with Key Forwarding `ssh -A` but I have not tried it.

---

<div class="post-metadata">

**Author:** ![justinsixty](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@justinsixty](https://discuss.circleci.com/u/justinsixty)\
**Post date:** [November 18, 2015, 4:48pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/11 "2015-11-18T16:48:31Z")

</div>

I added the keys to Github but am still having issues logging in. Below is the verbose logging that I get…Is there something I am still doing wrong?

ubuntu@ip-172-31-44-230:~/.ssh$ ssh -vvv -p 64662 [ubuntu@54.167.183.91](mailto:ubuntu@54.167.183.91)  
OpenSSH\_6.6.1, OpenSSL 1.0.1f 6 Jan 2014  
debug1: Reading configuration data /etc/ssh/ssh\_config  
debug1: /etc/ssh/ssh\_config line 19: Applying options for \*  
debug2: ssh\_connect: needpriv 0  
debug1: Connecting to 54.167.183.91 [54.167.183.91] port 64662.  
debug1: Connection established.  
debug3: Incorrect RSA1 identifier  
debug3: Could not load “/home/ubuntu/.ssh/id\_rsa” as a RSA1 public key  
debug1: identity file /home/ubuntu/.ssh/id\_rsa type 1  
debug1: identity file /home/ubuntu/.ssh/id\_rsa-cert type -1  
debug1: identity file /home/ubuntu/.ssh/id\_dsa type -1  
debug1: identity file /home/ubuntu/.ssh/id\_dsa-cert type -1  
debug1: identity file /home/ubuntu/.ssh/id\_ecdsa type -1  
debug1: identity file /home/ubuntu/.ssh/id\_ecdsa-cert type -1  
debug1: identity file /home/ubuntu/.ssh/id\_ed25519 type -1  
debug1: identity file /home/ubuntu/.ssh/id\_ed25519-cert type -1  
debug1: Enabling compatibility mode for protocol 2.0  
debug1: Local version string SSH-2.0-OpenSSH\_6.6.1p1 Ubuntu-2ubuntu2  
debug1: Remote protocol version 2.0, remote software version OpenSSH\_5.9p1 Debian-5ubuntu1.7  
debug1: match: OpenSSH\_5.9p1 Debian-5ubuntu1.7 pat OpenSSH\_5\* compat 0x0c000000  
debug2: fd 3 setting O\_NONBLOCK  
debug3: put\_host\_port: [54.167.183.91]:64662  
debug3: load\_hostkeys: loading entries for host “[54.167.183.91]:64662” from file "/home/ubuntu/.ssh/known\_hosts"  
debug3: load\_hostkeys: found key type ECDSA in file /home/ubuntu/.ssh/known\_hosts:98  
debug3: load\_hostkeys: loaded 1 keys  
debug3: order\_hostkeyalgs: prefer hostkeyalgs: [ecdsa-sha2-nistp256-cert-v01@openssh.com](mailto:ecdsa-sha2-nistp256-cert-v01@openssh.com),ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521  
debug1: SSH2\_MSG\_KEXINIT sent  
debug1: SSH2\_MSG\_KEXINIT received  
debug2: kex\_parse\_kexinit: [curve25519-sha256@libssh.org](mailto:curve25519-sha256@libssh.org),ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1  
debug2: kex\_parse\_kexinit: [ecdsa-sha2-nistp256-cert-v01@openssh.com](mailto:ecdsa-sha2-nistp256-cert-v01@openssh.com),ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-ed25519,ssh-rsa,ssh-dss  
debug2: kex\_parse\_kexinit: [aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com](mailto:aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com),aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se  
debug2: kex\_parse\_kexinit: [aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com](mailto:aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com),aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se  
debug2: kex\_parse\_kexinit: [hmac-md5-etm@openssh.com](mailto:hmac-md5-etm@openssh.com),hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96  
debug2: kex\_parse\_kexinit: [hmac-md5-etm@openssh.com](mailto:hmac-md5-etm@openssh.com),hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96  
debug2: kex\_parse\_kexinit: [none,zlib@openssh.com](mailto:none,zlib@openssh.com),zlib  
debug2: kex\_parse\_kexinit: [none,zlib@openssh.com](mailto:none,zlib@openssh.com),zlib  
debug2: kex\_parse\_kexinit:  
debug2: kex\_parse\_kexinit:  
debug2: kex\_parse\_kexinit: first\_kex\_follows 0  
debug2: kex\_parse\_kexinit: reserved 0  
debug2: kex\_parse\_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1  
debug2: kex\_parse\_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256  
debug2: kex\_parse\_kexinit: [aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se](mailto:aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se)  
debug2: kex\_parse\_kexinit: [aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se](mailto:aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se)  
debug2: kex\_parse\_kexinit: [hmac-md5,hmac-sha1,umac-64@openssh.com](mailto:hmac-md5,hmac-sha1,umac-64@openssh.com),hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96  
debug2: kex\_parse\_kexinit: [hmac-md5,hmac-sha1,umac-64@openssh.com](mailto:hmac-md5,hmac-sha1,umac-64@openssh.com),hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96  
debug2: kex\_parse\_kexinit: [none,zlib@openssh.com](mailto:none,zlib@openssh.com)  
debug2: kex\_parse\_kexinit: [none,zlib@openssh.com](mailto:none,zlib@openssh.com)  
debug2: kex\_parse\_kexinit:  
debug2: kex\_parse\_kexinit:  
debug2: kex\_parse\_kexinit: first\_kex\_follows 0  
debug2: kex\_parse\_kexinit: reserved 0  
debug2: mac\_setup: setup hmac-md5  
debug1: kex: server-\>client aes128-ctr hmac-md5 none  
debug2: mac\_setup: setup hmac-md5  
debug1: kex: client-\>server aes128-ctr hmac-md5 none  
debug1: sending SSH2\_MSG\_KEX\_ECDH\_INIT  
debug1: expecting SSH2\_MSG\_KEX\_ECDH\_REPLY  
debug1: Server host key: ECDSA f2:ad:7f:04:b7:4f:75:08:60:68:f2:c3:69:0f:db:d3  
debug3: put\_host\_port: [54.167.183.91]:64662  
debug3: put\_host\_port: [54.167.183.91]:64662  
debug3: load\_hostkeys: loading entries for host “[54.167.183.91]:64662” from file "/home/ubuntu/.ssh/known\_hosts"  
debug3: load\_hostkeys: found key type ECDSA in file /home/ubuntu/.ssh/known\_hosts:98  
debug3: load\_hostkeys: loaded 1 keys  
debug3: load\_hostkeys: loading entries for host “[54.167.183.91]:64662” from file "/home/ubuntu/.ssh/known\_hosts"  
debug3: load\_hostkeys: found key type ECDSA in file /home/ubuntu/.ssh/known\_hosts:98  
debug3: load\_hostkeys: loaded 1 keys  
debug1: Host ‘[54.167.183.91]:64662’ is known and matches the ECDSA host key.  
debug1: Found key in /home/ubuntu/.ssh/known\_hosts:98  
debug1: ssh\_ecdsa\_verify: signature correct  
debug2: kex\_derive\_keys  
debug2: set\_newkeys: mode 1  
debug1: SSH2\_MSG\_NEWKEYS sent  
debug1: expecting SSH2\_MSG\_NEWKEYS  
debug2: set\_newkeys: mode 0  
debug1: SSH2\_MSG\_NEWKEYS received  
debug1: Roaming not allowed by server  
debug1: SSH2\_MSG\_SERVICE\_REQUEST sent  
debug2: service\_accept: ssh-userauth  
debug1: SSH2\_MSG\_SERVICE\_ACCEPT received  
debug2: key: /home/ubuntu/.ssh/id\_rsa (0x7fdebfa8a990),  
debug2: key: /home/ubuntu/.ssh/id\_dsa ((nil)),  
debug2: key: /home/ubuntu/.ssh/id\_ecdsa ((nil)),  
debug2: key: /home/ubuntu/.ssh/id\_ed25519 ((nil)),  
debug1: Authentications that can continue: publickey  
debug3: start over, passed a different list publickey  
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password  
debug3: authmethod\_lookup publickey  
debug3: remaining preferred: keyboard-interactive,password  
debug3: authmethod\_is\_enabled publickey  
debug1: Next authentication method: publickey  
debug1: Offering RSA public key: /home/ubuntu/.ssh/id\_rsa  
debug3: send\_pubkey\_test  
debug2: we sent a publickey packet, wait for reply  
debug1: Authentications that can continue: publickey  
debug1: Trying private key: /home/ubuntu/.ssh/id\_dsa  
debug3: no such identity: /home/ubuntu/.ssh/id\_dsa: No such file or directory  
debug1: Trying private key: /home/ubuntu/.ssh/id\_ecdsa  
debug3: no such identity: /home/ubuntu/.ssh/id\_ecdsa: No such file or directory  
debug1: Trying private key: /home/ubuntu/.ssh/id\_ed25519  
debug3: no such identity: /home/ubuntu/.ssh/id\_ed25519: No such file or directory  
debug2: we did not send a packet, disable method  
debug1: No more authentication methods to try.  
Permission denied (publickey).  
ubuntu@ip-172-31-44-230:~/.ssh$

---

<div class="post-metadata">

**Author:** ![levlaz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/levlaz/32/36978_2.png) [@levlaz](https://discuss.circleci.com/u/levlaz)\
**Post date:** [November 18, 2015, 11:09pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/12 "2015-11-18T23:09:21Z")

</div>

What happens if you run this command from that box

`ssh git@github.com`

---

<div class="post-metadata">

**Author:** ![Saneyan](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/saneyan/32/1688_2.png) [@Saneyan](https://discuss.circleci.com/u/Saneyan)\
**Post date:** [February 21, 2016, 5:19am UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/13 "2016-02-21T05:19:04Z")

</div>

Recently, I tried to connect to Circle CI container via SSH. I usually use ED25519 key to authorize my account on GitHub. Although the container seems not to support ED25519 format, it accepts ECDSA key format.

So, I checked the OpenSSH version on Circle CI container. This version is `5.9p1`. OpenSSH supports ED25519 format after version `6.5`.

---

<div class="post-metadata">

**Author:** ![glesage](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/glesage/32/1224_2.png) [@glesage](https://discuss.circleci.com/u/glesage)\
**Post date:** [May 17, 2016, 7:30pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/14 "2016-05-17T19:30:07Z")

</div>

Still getting the same issue…

```auto
ssh git@github.com
...
Hi glesage! You've successfully authenticated, but GitHub does not provide shell access.
Connection to github.com closed.

```

for circle-ci `ssh -vvv -p $PORT distiller@$IP`

```auto
OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 162.217.87.107 [162.217.87.107] port 55005.
debug1: Connection established.
debug1: identity file /Users/glesage/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/glesage/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.9
debug1: match: OpenSSH_6.9 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 162.217.87.107:55005 as 'distiller'
debug3: put_host_port: [162.217.87.107]:55005
debug3: hostkeys_foreach: reading file "/Users/glesage/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/glesage/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys from [162.217.87.107]:55005
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:mnxfGWC9fJVfsTDk6NlCtBkKuF6jAkxKMDNKZRheYUc
debug3: put_host_port: [162.217.87.107]:55005
debug3: put_host_port: [162.217.87.107]:55005
debug3: hostkeys_foreach: reading file "/Users/glesage/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/glesage/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys from [162.217.87.107]:55005
debug3: hostkeys_foreach: reading file "/Users/glesage/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /Users/glesage/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys from [162.217.87.107]:55005
debug1: Host '[162.217.87.107]:55005' is known and matches the RSA host key.
debug1: Found key in /Users/glesage/.ssh/known_hosts:3
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /Users/glesage/.ssh/id_rsa (0x7fb202f003b0),
debug2: key: /Users/glesage/.ssh/id_dsa (0x0),
debug2: key: /Users/glesage/.ssh/id_ecdsa (0x0),
debug2: key: /Users/glesage/.ssh/id_ed25519 (0x0),
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/glesage/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/glesage/.ssh/id_dsa
debug3: no such identity: /Users/glesage/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /Users/glesage/.ssh/id_ecdsa
debug3: no such identity: /Users/glesage/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /Users/glesage/.ssh/id_ed25519
debug3: no such identity: /Users/glesage/.ssh/id_ed25519: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

```

---

<div class="post-metadata">

**Author:** ![btbailey](https://avatars.discourse-cdn.com/v4/letter/b/258eb7/32.png) [@btbailey](https://discuss.circleci.com/u/btbailey)\
**Post date:** [May 18, 2016, 5:15pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/15 "2016-05-18T17:15:01Z")

</div>

I am encountering the same exact issue as you currently, and do not have the “Debug via SSH” tab on my build UI (attached). Not sure what to make of this.  
[pic1](https://www.evernote.com/l/ABay9_7-JGxNebWUmkZdOc3ALmlVxqFK3cQB/image.png)  
[pic2](https://www.evernote.com/l/ABYP7YVxMeBIQ4paFd7HTVmi4U8Buh3r3DgB/image.png)

---

<div class="post-metadata">

**Author:** ![turbomerl](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@turbomerl](https://discuss.circleci.com/u/turbomerl)\
**Post date:** [May 19, 2016, 9:30am UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/16 "2016-05-19T09:30:43Z")

</div>

I am also having this same issue. Authenticate fine with github, but the debug via ssh tab is not visible and have the same problems trying to ssh to the build as the above posters.

---

<div class="post-metadata">

**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\
**Post date:** [May 19, 2016, 12:16pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/17 "2016-05-19T12:16:51Z")

</div>

@turbomerl @btbailey Just to check as a first step:

In order to see the ‘debug via SSH tab’ on a project owned by another organization your GitHub account must have write permissions for that repository (GitHub repo \> Settings \> Collaboarators and Teams)

This can sometimes take a few minutes to propagate - and may require you to log out of CircleCI and GitHub and then log back in again.

Some more info here: [https://circleci.com/docs/github-permissions/](https://circleci.com/docs/github-permissions/)

---

<div class="post-metadata">

**Author:** ![turbomerl](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@turbomerl](https://discuss.circleci.com/u/turbomerl)\
**Post date:** [May 19, 2016, 1:45pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/18 "2016-05-19T13:45:08Z")

</div>

Thanks for the reply @tom . This project is owned by my organization - I have added the team (of which my account is a member) under the github section you mention anyway. I logged out of both platforms and gave it a few minutes, but I still don’t see the tab, or am able to ssh to the build. If I log out and log in again, I see the tab there very briefly and then it vanishes when the page is fully loaded.

Your help on this is very much appreciated 😃

---

<div class="post-metadata">

**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\
**Post date:** [May 19, 2016, 2:43pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/19 "2016-05-19T14:43:54Z")

</div>

@turbomerl Thanks for checking that. One more thing I should have asked - is this an OS X build? If so, rebuild with SSH does not show by default.

---

<div class="post-metadata">

**Author:** ![turbomerl](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@turbomerl](https://discuss.circleci.com/u/turbomerl)\
**Post date:** [May 20, 2016, 2:11pm UTC](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558/20 "2016-05-20T14:11:24Z")

</div>

Hi @tom - yes it is OS X

[Next page](https://discuss.circleci.com/t/cant-ssh-into-build-machine/558.md?page=2)