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
There should not be any reason why stopping and starting the container would affect the api key persisting. It is saved to the browser, not the server.
If you are instead saying that moving between multiple browsers do not persist the key, that is a known limitation of using a client-side UI instead of a server-side one. It cannot be fixed without a far more complex and potentially less secure rearchitecture of the UI.
Is there anyway to persist the APIKEY once I've added it to settings?
Every time I stop and start the headscaleUI container I have to re-add it again.
It would even be great if we could add it in as an environment variable to the container.
Thanks
The text was updated successfully, but these errors were encountered: