The key_load_public bits are a red herring; it loads id_rsa(.pub) successfully (you can tell because it says "type 1", not "type -1"), and the immediately-subsequent error pertains to id_rsa-cert(.pub) instead. So it's successfully loaded the available identity file.
I think the next steps here should have been: * increase debugging to -vvv rather than just -vv (no point in messing about, might as well have the maximum debugging level) * see if there's any useful logging at the server end if you have root access to it, probably in /var/log/auth.log However, it seems that the network fix was sufficient? I would say that a hang is a fairly typical response to a misconfigured network. ssh's debugging output is primarily intended for developers, and I don't think we (or upstream) would generally consider it a bug that it may require reading the source code to determine what it means. ** Summary changed: - unable to connect or load identity file + unable to connect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534792 Title: unable to connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1534792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
