Twingate Connector Issue on QNAP Docker Deployment

Support / Troubleshooting
1

Hi all,

I’m using Docker on a QNAP TS-231P to deploy Twingate Connector. My Docker container is up and running successfully, but my connector doesn’t connect to my Twingate Network. Can anyone help me debug this issue?

My TWINGATE_NETWORK is set to “nharua.”

I’ve observed the following logs:
$ docker logs a242d284bcc5
State: Offline
State: Authentication
[msg] Nameserver 127.0.0.11:53 has failed: request timed out.
[msg] All nameservers have failed
State: Error
State: Offline
State: Authentication
State: Error
State: Offline
State: Authentication
State: Error
State: Offline
State: Authentication
[msg] Nameserver 127.0.0.11:53 is back up
[msg] Nameserver 127.0.0.11:53 has failed: request timed out.
[msg] All nameservers have failed
[msg] Nameserver 127.0.0.11:53 is back up

The health check status shows as “healthy”:
$ docker inspect --format “{{json .State.Health }}” a242d284bcc5
{“Status”:“healthy”,“FailingStreak”:0,“Log”:[{“Start”:“2023-10-17T13:52:35.94386604+07:00”,“End”:“2023-10-17T13:52:36.22773022+07:00”,“ExitCode”:0,“Output”:“OK\n”},{“Start”:“2023-10-17T13:52:46.35176532+07:00”,“End”:“2023-10-17T13:52:46.58092936+07:00”,“ExitCode”:0,“Output”:“OK\n”},{“Start”:“2023-10-17T13:52:56.69361852+07:00”,“End”:“2023-10-17T13:52:56.93123014+07:00”,“ExitCode”:0,“Output”:“OK\n”},{“Start”:“2023-10-17T13:53:07.1109781+07:00”,“End”:“2023-10-17T13:53:07.34350798+07:00”,“ExitCode”:0,“Output”:“OK\n”},{“Start”:“2023-10-17T13:53:17.45465376+07:00”,“End”:“2023-10-17T13:53:17.7855731+07:00”,“ExitCode”:0,“Output”:“OK\n”}]}

The Twingate Connector version is 1.60.0:
$ docker exec twingate-quartz-prawn ./connectord --version
1.60.0

Thanks and Regards,
Vinh

2

Hey Vinh,

The logs seem to suggest a DNS specific issue. However that may be misleading.

I just want to clarify - do you have your TWINGATE_NETWORK set to nharua. or nharua (with or without the trailing period)

If it has the period, try removing that and see if anything changes.

You can also put the connector into DEBUG logging mode which may provide more information on what is truly failing.

Let me know!

Thanks,

-arthur

3

Hi,
This is my conf

image
image1619×311 14.4 KB

Btw,
My connector is now up and running successfully after several reboot processes and I’m not sure why It is connected.

Thanks,
Vinh

4

The snippet you posted looks correct, and if the connector is up and running it must be correct! :smiley: For now I’d say lets wait and see if it goes bork again, but if it keeps working, we’ll chalk it up to computers being computers!

Thanks,

arthur