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
Last night, my server auto-updated the tsdprox container. After the container restart, tsdproxy (tried) to recreate the already existing machines. The problem with the recreation is either:
if the auth key is already expired, creation of the machine fails or
the machine gets a different name by adding a suffix like "-1" for example.
Therefore, I would like tsdproxy to prevent the creation of machines that already exist. Is that possible? Another solution could be the use of never expiring OAuth ephemeral nodes?!
Thx a lot for the great software! 😊
The text was updated successfully, but these errors were encountered:
Came here to say I had this same issue this morning.
I stopped the TSDProxy container and then removed all the created machines from my TS dashboard. Restarted and back to usual.
It made me think of another possibly feature — a TSDProxy script/command to purge all created containers created by TSDProxy from Tailscale. Could be very helpful if the initial issue is hard to avoid ongoing.
I have ephemeral activated and still ended up with -1 names. (and ephemeral is the default, right? On my tailscale dashboard, the tsdproxy machines all have the blue label)
Hi everyone,
Last night, my server auto-updated the tsdprox container. After the container restart, tsdproxy (tried) to recreate the already existing machines. The problem with the recreation is either:
Therefore, I would like tsdproxy to prevent the creation of machines that already exist. Is that possible? Another solution could be the use of never expiring OAuth ephemeral nodes?!
Thx a lot for the great software! 😊
The text was updated successfully, but these errors were encountered: