-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Auto-reconnect does not work in 0.71.0.2 #23
Comments
Yes, I have the same problem! So, I suggest to add the option to enforce a reconnection, even if the client doesn't see that the connection is closed (that's quite easy: the client disconnects and reconnects... the disconnect action never fails even when it's really disconnected). Regards. |
Unfortunately I was not able to reproduce your issue, with or without "reconnect on system wakeup enabled". |
Hi @cyd01 , I'm using the Portable binary with certificates and with passwords. I'm not sure, but the problem seems to appears only using one of the two modes. I'll try to provide a more detailed description. Regards. |
I'm blind. But i've tried to modify something.
Can you test this beta build: https://www.9bis.net/kitty/data/beta/kitty.exe
?
Thanks for your help
Cyd
Le lun. 10 juin 2019 à 21:32, pszlazak <notifications@github.com> a écrit :
… HI @cyd01 <https://github.com/cyd01>,
I'm on Windows 10 1903. And, same as @lars18th
<https://github.com/lars18th>, I'm using portable version. Although for
me, it does not matter if I'm using ssh key or password based login. In
both cases connection is not auto-reconnected after I put my PC to sleep.
Regards!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AIESOBQOW5VSQ6GDFAB6NSLPZ2T4BA5CNFSM4HVHGUDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXK7SSA#issuecomment-500562248>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBU5CNTAQ57OAXOWV63PZ2T4BANCNFSM4HVHGUDA>
.
|
Hi! The beta doesn't solve it for me. I currently test it by disabling the network interface shortly. 0.70.0.9: Works as expected. All versions do seem to detect the network loss directly (icon directly changes to the disconnect variant), but only the 0.70 version actually displays "(inactive)" as title, while the 0.71 variants still display the shell title. Edit: I'm using the classic variant btw, happens with both key and password authentication. |
Also no luck here (with beta). |
Event logs for 0.70.0.10: For 0.71.0.3: And for 0.71.0.3.beta: I can provide full event logs, if needed. |
Can you test this new build: https://www.9bis.net/kitty/data/beta/kitty.exe
?
(thanks to my friend leo that reproduced the issue and found something in
the restart message).
Le lun. 10 juin 2019 à 22:44, pszlazak <notifications@github.com> a écrit :
… Event logs for *0.70.0.10*:
...
2019-06-10 22:32:28 Started a shell/command
2019-06-10 22:32:53 Connection closed by remote host
2019-06-10 22:32:53 Network error: Software caused connection abort
2019-06-10 22:32:53 KiTTY Fatal Error: Network error: Software caused
connection abort
2019-06-10 22:33:11 No connection on key pressed, trying to reconnect...
2019-06-10 22:33:11 ----- Session restarted -----
2019-06-10 22:33:11 Connecting to 192.168.2.214 port 22
...
For *0.71.0.3*:
...
2019-06-10 22:32:33 Started a shell/command
2019-06-10 22:32:53 Network error: Network error: Software caused
connection abort
<nothing more>
And for *0.71.0.3.beta*:
...
2019-06-10 22:32:38 Started a shell/command
2019-06-10 22:32:53 Network error: Network error: Software caused
connection abort
<nothing more>
I can provide full event logs, if needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AIESOBRI7EUHZRHIUO5C4PTPZ24LLA5CNFSM4HVHGUDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLFWFA#issuecomment-500587284>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBX2MHWAM2QRJAUNXVDPZ24LLANCNFSM4HVHGUDA>
.
|
Works like a charm! |
I can also confirm that this build fixes the reconnection problem 😃 |
Thanks for your help
Le mar. 11 juin 2019 à 18:27, Bob van de Vijver <notifications@github.com>
a écrit :
… I can also confirm that this build fixes the reconnection problem 😃
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AIESOBTDTEGHE5HC4DIOQCTPZ7G5JA5CNFSM4HVHGUDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXNWYXY#issuecomment-500919391>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBS7RLRUGGFU3UYMVWDPZ7G5JANCNFSM4HVHGUDA>
.
|
Is there also a way to reconnect manually with 0.71? In the past restart session helped in this case, really liked the option :-) |
Hi @hnz101,
Yes, this is a bug. Please try beta version provided by cyd01:
|
Oh you're right, didn't see this part. @pszlazak thank you guys! |
Hi @cyd01 , Thank you! In version 0.71.0.4 it works. 👍 However, I detected that in some cases when reconnecting the old password is not used Regards. |
Hi @cyd01 , Before close this issue, I have a related trouble (but not directly the same): When connecting over a Socks Proxy (created with a Dynamic forwarding of another KiTTY session), when the Proxy fails KiTTY doesn't detects that the session is closed. So, we can't reconnect. Please, can you review the code when connecting over a Socks Proxy? Thank you! |
Hi,
I'm the only one experimenting this issue? |
I've started to fix it by adding a new menu item "Restart session". |
Thank you! Now testing it... Comments:
|
Hi @cyd01 , From my point of view this new beta with "Restart session" works wihtout troubles. My suggestion is to release a new version v0.71.0.5 with this change (and perhaps others). You agree? |
I agree. I've also fixed issues with Font resizing and Black&White colors.
I've also changed the menu item to Close & Connect as you've suggested.
Le jeu. 27 juin 2019 à 14:49, Lars The <notifications@github.com> a écrit :
… Hi @cyd01 <https://github.com/cyd01> ,
From my point of view this new beta with "Restart session" works wihtout
troubles. My suggestion is to release a new version v0.71.0.5 with this
change (and perhaps others).
You agree?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AIESOBS36KY4IG7VANWXYJDP4SZL3A5CNFSM4HVHGUDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXAEHA#issuecomment-506331676>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBTYKGSEV2RQQW6WFRLP4SZL3ANCNFSM4HVHGUDA>
.
|
Hi, Perhaps the version 0.71.0.5 not fixes the problem entirely. But I suggest to close this issue, and reopen another if the problem continues but using this new version. As the code handle has changed it's possible that the behaviour has changed too. You agree? |
To be closed IMHO. Original problem solved in 0.71.0.4. |
Then, please @pszlazak select "CLOSE", as only you (and the main developer) can close the issue. 😉 |
Initial problem with auto-reconnect solved in Additional functionality requested by @lars18th to add 'Close+Restart' option in menu delivered in |
Hello,
There is a problem with auto-reconnect function in 0.71.0.2.
If I put my PC to sleep and it wakes up, connection is broken, but looks like it's not detected, as in menu I can only see option to duplicate session, but not to restart session.
Hence clicking or pressing keyboard button does not restart the session.
Strangely, if option to reconnect on system wakeup is enabled, it works.
Previously auto-reconnect was working even without reconnect on system wakeup enabled.
Problem is also mentioned here #22 and here #15 (comment).
The text was updated successfully, but these errors were encountered: