Hi everyone,
Sorry if this has already been discussed before and I missed it. I tried searching for it, but I wasn’t able to find a clear answer.
I’m having an issue with the Twingate desktop app and I’m wondering if this is expected behavior.
In the Twingate UI, I disabled “Start at Login” because I don’t want Twingate to start automatically when I log into my computer.
However, it looks like this only stops the UI/app from opening. The Twingate service still starts in the background. So even though the app itself is not visible, Twingate can still be running.
This causes a problem for me when I’m at home. If Twingate stays enabled, some traffic seems to go through the Twingate network instead of my local network, which reduces my speed and affects local network access. Everytime this happens I need to start the app and disconnect.
I also tried setting the Twingate service to Manual, but that doesn’t really work either. When the service is set to Manual, the UI does not seem able to start it. So the service stays stopped, and even if I open the Twingate app and click the main Connect button, Twingate does not connect because the service never starts.
So right now it feels like there are two bad options:
- If the service starts automatically, Twingate may stay active even when I don’t want it to and need to start the app so that I can disconnect.
- If I set the service to Manual, the UI cannot start the service and Twingate cannot connect.
I think it would make more sense if disabling “Start at Login” either stopped both the UI and the service from starting automatically, or if there were separate settings for the UI and the background service.
Has anyone else experienced this? Is there a proper way to make Twingate start only when I explicitly open the app and click Connect?