Robomongo: Error: Resources temporarily unavailable. Error when starting up SSH session: -8 . (Error #11)

[mu-hasan]

Last week I can connect via SSH tunnel to my server. And for now, I still can connect to my server via SSH with CLI. But I got error when I use robo3T

Specification:

• Laptop : Linux Elementary OS / Ubuntu 16.04
• Server : RedHat 7.0
• MongoDB : v3.4.5
• Robo3T : v1.1.1

[esodell1]

I'm having this same issue. I read about similar issues that got resolved in v1.1, but it didn't seem to fix this issue for me. I am also able to ssh in via terminal just fine.

Error:
Resource temporarily unavailable. Error when starting up SSH session: -8
. (Error #35)

Mac OS 10.12
Robo 3T 1.1.1
MongoDB 3.4.6

[BarryHelfrich]

Same error when updating to OpenSSH_7.4p1 on Centos 7.4

/var/log/secure error: kex protocol error: type 30 seq 1

Looks like the SSH library in R3T is using a key exchange algo deprecated with up to date sshd configs.

[angwe]

Having same issue. MongoDBs are on RH7 servers. SSH tunnel won't open. Seconding @BarryHelfrich 's analysis.

[zendu]

I face same issue. Here is my configuration

Robo3T 1.1.1 on Window 10 (Microsoft Windows [Version 10.0.10586])

MongoDB 3.2.8 on Red Hat Enterprise Linux Server release 7.3 (Maipo)

[angwe]

If I connect an SSH tunnel via some other SSH mechanism, Robo 3T has no problems. A small SSH-related update would be most appreciated.

[angwe]

Still have same problem, Mac or Windows, whatever version of Mongo. There's still a bad encryption choice in the SSH library in Robo 3T.

Windows 8 / Mac OS X 10.11
RedHat Enterprise Linux 7.4
MongoDB 3.4.10

[simsekgokhan]

Hi All, please see the beta prepared for this problem, seems to be working for couple of people. See comment: https://github.com/Studio3T/robomongo/issues/1189#issuecomment-353279070

[jasonk]

I realize this ticket is a couple of years old, but since it's still open and people are still finding it via Google I thought I'd add in that in my case the error we were seeing was Resource temporarily unavailable. Authentication by key (/path/to/id_rsa) failed (Error -16). (Error #35). If this is the error you are encountering, the problem is that Robo 3T doesn't seem to be capable of using an unencrypted key.

[HishamMubarak]

I realize this ticket is a couple of years old, but since it's still open and people are still finding it via Google I thought I'd add in that in my case the error we were seeing was Resource temporarily unavailable. Authentication by key (/path/to/id_rsa) failed (Error -16). (Error #35). If this is the error you are encountering, the problem is that Robo 3T doesn't seem to be capable of using an unencrypted key.

Thanks a lot. This helped :)

[marceloschmidt]

I am still getting this error on Ubuntu 20.04; Robo3T version 3.14 (not on snap, so the problem of accessing hidden folder is not the issue). I have a password protected id_rsa, but still get Resource temporarily unavailable. Authentication by key (/home/marcelo/.ssh/id_rsa) failed (Error -16). (Error #11).

[adantoscano]

Same here, getting this error with both pass and key, using Ubuntu 18.04 Error: Resource temporarily unavailable. Error when starting up SSH session: -8 . (Error #11)

[CherryDT]

Solution for the -8 error: Add KexAlgorithms +diffie-hellman-group1-sha1 to the tunnel server's /etc/ssh/sshd_config file. (Note: Degrades security.)

[emanoelcarlos]

Try to update your robo3t to version 1.4+. I was facing the same problem on ubuntu 20.04 (but not on ubuntu 18.04) and it works fine now.