-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug] macOS unable to connect, node has an open stream(..), rejecting new stream #1942
Comments
This is a log of a node that is affected. I'm not sure if this is related to Headscale or the Tailscale client though.
|
When I try to delete an affected node in Headscale, I'm getting the following error:
After a restart of Headscale, it works fine. |
This is issue is same as #1930. Problem may occur on any client regardless to OS. Restarting headscale temporarily solves connection problem. |
@winterheart that seems correct. Somehow GitHub didn't show that issue when searching for the error in the log. |
This happens to me as well. Or at least something similar (?) My headscale is on an i386 netbook with Debian GNU/Linux 11 (bullseye) i686. Whatever method I use to register my nodes (browser, or auth key), whatever is their type (Linux, Android, Windows, iOS), they all start up Of course I choose for my headscale URL a free port.
My nodes list
|
I also had a similar issue just now, first time it happened, though it seems my Tailscale is a bit less reliable recently. All my traffic from my phone (Android) is shuttled through an exit node. I was playing some Genshin Impact when the game disconnected. After restarting the game, I couldn't even login. Then I tried to access anything in my browser (both pages on the wide web as well as those I have behind the VPN) and nothing connected either. Restarting the phone and trying to reconnect to the VPN produced the same "node has an open stream" as above. Restarting headscale helped. The other bug was closed after someone suggested updating the Android client to 1.66.3, but I'm already at that version. Headscale is up to date. Let me know if there's anything else that would be helpful to provide. |
Is this a support request?
Is there an existing issue for this?
Current Behavior
I'm currently experiencing issues with macOS nodes that when switching networks (for example from wired to wireless) or coming back out of sleep, the client is unable to connect to Headscale. Restarting the client doesn't help.
The log is showing the following:
Restarting Headscale helps. I guess this clears all the current sessions known by Headscale.
Expected Behavior
The client should reconnect succesfully.
Steps To Reproduce
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: