![]() ![]() ![]() ![]() 16:21:57.702734500 debug1: userauth_pubkey: test whether pkalg/pkblob are acceptable for RSA SHA256:WeR8Jg0aacxvfW94RjNJ5VX/va50ZoQ7vQJad4lalws 16:21:57.702656500 debug1: userauth-request for user root service ssh-connection method publickey 16:21:57.695408500 debug1: userauth-request for user root service ssh-connection method none My guess is some openssh lib update probably broke the integration.Įdit: Robo 3T 1.2 Beta fix posted above also fixes the issue for me. We use Amazon Linux - could test by spawning a brand new Amazon Linux AMI, running sudo yum update and install mongo on it, and see if you can connect. Would have to scour logs on server side to see if we can track something down. My guess is something changed in the openssh server libs and people only see it if they get that update, which causes the problem. Since that time, we can no longer tunnel with Robo 3T, but we can still connect just fine using Mac Terminal. The other thing I did was a sudo yum update on the servers, so it's very likely openssh or other related libs probably got upgraded. Yesterday we had an issue where I had to step down our Primary in the replica set and elect a new primary, so our replica set status got jogged around a bit, but IP addresses remained the same. We use Robo 3T probably daily for years and the SSH tunnel has always just worked. Actually corroborated also with a co-worker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |