You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed I got "Error: read: Connection reset by peer" every time the application has issues reading my .ssh/config file.
For example, if I had comments at the end of a line, like:
LocalForward 2101 10.0.0.99:9909 # xxxx server VNC
It will trigger the problem, but if I change it to:
# xxxx server VNC
LocalForward 2101 10.0.0.99:9909
it will work... (note that neither ssh or scp are having any issue with those parameters).
Now I'm having the issue again, and I suspect this is the same kind of parsing problem (I can connect if I rename my .ssh/config before clicking the "connect" button) but I cannot figure out which of the 350+ lines in my .ssh/config is causing issues (and I'd prefer not having to strip all comments because it would become unmaintainable).
I'd like to give more details but if some issues mention a "debug mode" that displays more information, I couldn't find out how to activate it.
The text was updated successfully, but these errors were encountered:
I noticed I got "Error: read: Connection reset by peer" every time the application has issues reading my .ssh/config file.
For example, if I had comments at the end of a line, like:
It will trigger the problem, but if I change it to:
it will work... (note that neither ssh or scp are having any issue with those parameters).
Now I'm having the issue again, and I suspect this is the same kind of parsing problem (I can connect if I rename my .ssh/config before clicking the "connect" button) but I cannot figure out which of the 350+ lines in my .ssh/config is causing issues (and I'd prefer not having to strip all comments because it would become unmaintainable).
I'd like to give more details but if some issues mention a "debug mode" that displays more information, I couldn't find out how to activate it.
The text was updated successfully, but these errors were encountered: