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
Describe the bug
If a project's tailscale connection is broken for more than 5 minutes (e.g. the server is stopped for more than 5 minutes), the connection can not be reestablished. This is due to how the headscale server is configured and due to the fact that projects use ephemeral network keys.
To Reproduce
Steps to reproduce the behavior:
Run the Daytona Server
Create a workspace and observe that you can use daytona ssh/code to connect to it.
Stop the Daytona Server for more than 5 minutes, then start it again
Observe that you can not connect to the same workspace you created in step 2.
Expected behavior
Projects should be able to reestablish a connection to the server no matter how long the connection was broken for.
Desktop (please complete the following information):
OS: any
Daytona Version: v0.14.0
Additional context
There are 3 possible solutions to the issue:
Solution 2 seems very exact. It will require a bit more effort, but in the end, the workspace removal can require a cleanup anyway.
Agreed. I would suggest that the user of the auth key becomes PROJECT_NAME-WORKSPACE_ID (currently it's daytona for all keys), this way we can list, and then wipe, all the users keys with:
Describe the bug
If a project's tailscale connection is broken for more than 5 minutes (e.g. the server is stopped for more than 5 minutes), the connection can not be reestablished. This is due to how the headscale server is configured and due to the fact that projects use ephemeral network keys.
To Reproduce
Steps to reproduce the behavior:
daytona ssh/code
to connect to it.Expected behavior
Projects should be able to reestablish a connection to the server no matter how long the connection was broken for.
Desktop (please complete the following information):
Additional context
There are 3 possible solutions to the issue:
I favor approach 3 over 2, and avoid 1 as that could lead to node pileup on the headscale server.
The text was updated successfully, but these errors were encountered: