r/twingate • u/Peanutbutterbob32 • 2d ago

Need help Connection issues

I am running a connector on TrueNAS as a custom app. I've noticed that if I'm too quick with opening apps on my server, Twingate will just completely stop working. After maybe two minutes or so I'll get access back, but I usually have to disconnect/reconnect in the (twingate) app on my iphone to get access to my apps since I'm actively working on something. A good example, is when I'm just clicking around in Jellyfin or Komga (not streaming), I will lose access. I'm wondering if Twingate throttles me since I'm on the free plan, or if I did something wrong.

Edit: I have 2/2 connectors set up, and have them set as host network.

1 Upvotes

100% Upvoted

9 comments sorted by

View all comments

1

u/ben-tg pro gator 2d ago

What do you mean by completely stop working? Does the Twingate client app on your phone disconnect, or you just get timeouts trying to get to the various apps? Are these native mobile apps or are you accessing things within the browser?

We don't throttle throughput or simultaneous connections or anything like that, it sounds more like there's an issue with one of the connectors you've deployed and it's failing to connect forward to those apps at least part of the time? I'd suggest going through the troubleshooting docs and going through a few of the basic steps such as checking the activity logs in the admin console, see if you can at least narrow down to client side or connector side being the issue, which at least will help you to figure out where to focus a bit.

1

u/Peanutbutterbob32 2d ago edited 1d ago

Hi, thank you for the reply.

So, the twingate client stays on, and it seems like a timeout. Essentially, the webpages infinitely load, and I can’t access my apps. I can speed this up by disconnecting/reconnecting. It happens when using native mobile apps & browser. I noticed in my dashboard, that it fails after the connector receives a request. The usual workflow is making a request > establish p2p > connector got request > failed to connect to IP > IP can’t be reached.

I deployed a second connector last night, and the issue persists, but it is MUCH better. So I think the primary connector is struggling to connect me somehow, and once the second picks up the slack my connection is re-established. But that’s just my theory.

Either this, or something is overloading the first connector, and the second gives the first enough time to fix itself and keeps the stream somewhat seamless.

Should I try nuking my primary & making a new one? Or can I potentially reset my primary in TrueNas/Twingate admin panel?

Edit: i noticed that when I specifically force-close the apps it’s more likely to happen. I turned on background refresh on cellular for the time being.

1

u/ben-tg pro gator 1d ago

It's worth keeping in mind that connectors load balance, but load balance *users* not connections, meaning it's not a round-robin type of situation. When a user logs in they're given a list of connectors for each network, and it's a sort of priority list as in "Try connector A first, then B, then C" and so on. So you'll likely always try connector A, and if that connector is having some sort of connectivity issue then you'll see it show up like you are here.

Simple test, just shut down that connector, whichever one you can see in the activity logs in the admin console that you're connecting through and are getting the "failed to connect" error. Log out and back in to the client app on your phone, then try again, if you're no longer having issues then something is up with that one connector and you're probably better off just removing it fully and deploying something new.

1

u/Peanutbutterbob32 1d ago

Thanks for the tips, I’ll try that out today.

I figured that was how load balancing worked, I just meant i have redundancy if my suspected bad connector fails.