-
-
Notifications
You must be signed in to change notification settings - Fork 947
Session operation has timed out with version 2023.0.0 ok with 2020.0.2 #1260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry to hear that. Does it happen every time, or sporadically? There have been some issues reported here #1233 (comment). It might be worth a try. (edit: on second thoughts, that is about authentication, not connection) |
Happens every time, just time out. I have to revert at the minute as it's in production. |
If you are motivated to troubleshoot (understandable if not), the most definitive way would be to run a packet capture and observe differences between the old version and new. With Wireshark it's possible to filter on SSH packets https://wiki.wireshark.org/SSH.md |
Would like to add that although I use a different setup, I'm experiencing the same issue after upgrading from 2020.0.2 to 2023.0.0. Client setup similar to this:
I now see a version 2023.0.1 got released a few days ago. Does that one contain a potential fix? |
@AdalbertKhoolsaat please try 2023.0.1 and report back, thanks |
The 2023.0.1 version contains fixes that can help you. Please try new version. |
Alright, I have upgraded to the latest version but with mixed results. Debugging locally on a Windows machine it works, but once deployed on AWS Lambda (i.e. Amazon Linux 2) the issues still persist, albeit with a somewhat different error:
This setup worked without issues on 2020.0.2, so next attempt will be downgrading (for now). |
Turns out this error was caused by additional changes related to our provisioning on AWS (specifically, the Lambda had been placed inside a VPC). When put outside the VPC everything works as expected again using version 2023.0.1. |
Glad you got it sorted @Foxsterc I will close this one for now, but if you still see the same issue on 2023.0.1 feel free to re-open |
Apologies @Rob-Hague I've been away. I'm not in a position to test it ay the moment but I will try it as soon as I can. |
Hi,
I get the following error with version 2023.0.0
Session operation has timed out at Renci.SshNet.Session.WaitOnHandle(WaitHandle waitHandle, TimeSpan timeout) at Renci.SshNet.Session.WaitOnHandle(WaitHandle waitHandle) at Renci.SshNet.PrivateKeyAuthenticationMethod.Authenticate(Session session) at Renci.SshNet.AuthenticationMethod.Renci.SshNet.IAuthenticationMethod.Authenticate(ISession session) at Renci.SshNet.ClientAuthentication.TryAuthenticate(ISession session, AuthenticationState authenticationState, String[] allowedAuthenticationMethods, SshAuthenticationException& authenticationException) at Renci.SshNet.ClientAuthentication.Authenticate(IConnectionInfoInternal connectionInfo, ISession session) at Renci.SshNet.ConnectionInfo.Authenticate(ISession session, IServiceFactory serviceFactory) at Renci.SshNet.Session.Connect() at Renci.SshNet.BaseClient.CreateAndConnectSession() at Renci.SshNet.BaseClient.Connect()
With the following code
` var connectionInfo = new ConnectionInfo(this.Host,
`
The same code works fine with version 2020.0.2
Thanks,
The text was updated successfully, but these errors were encountered: