Can't authenticate user in Arch Linux

On my first setup of Twingate client for linux, everything works well until I run twingate start.

I get the following:

Starting Twingate service
Twingate has been started; user authentication is required for access to Resources
Starting UI notifications
Enabled desktop notifications

However, the client never authenticates and I get notifications “Authenticating” → “Offline” continuously. How do I force the client to authenticate?

Hey Fran,

Please try running /usr/bin/twingate-notifier console and see if you are given a URL to paste into a browser to complete the auth process.

Thanks,

-arthur

This is the output from the console:

Twingate Client Status: Authenticating
Twingate Client Status: Offline
Twingate Client Status: Authenticating
Twingate Client Status: Offline
Twingate Client Status: Authenticating

But I run systemctl status twingate and get this:

Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.172979+0000] [INFO] [client] [118489] Using DNS servers: '172.17.0.1, '
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.173002+0000] [INFO] [libsdwan][118489] set_dns: 172.17.0.1
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.902080+0000] [INFO] [client] [118489] Exiting on signal 15
Dec 06 16:03:14 fraruca systemd[1]: Stopping Twingate Remote Access Client...
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.963057+0000] [INFO] [libsdwan][118489] sdwan_state: Offline None
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.963124+0000] [INFO] [client] [118489] State: 'Offline', client mode: 'None'
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.964223+0000] [WARNING] [client] [118489] Failed to open '/etc/twingate/purge_file': 'No such file or dir>
Dec 06 16:03:14 fraruca twingated[118489]: [2023-12-06T16:03:14.964286+0000] [INFO] [client] [118489] Exiting Twingate Client
Dec 06 16:03:14 fraruca systemd[1]: twingate.service: Deactivated successfully.
Dec 06 16:03:15 fraruca systemd[1]: Stopped Twingate Remote Access Client.

Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.558086+0000] [INFO] [libsdwan][118807] sdwan_new: libsdwan_version=0.153.1, app_version=2023.338.105720,>
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.558326+0000] [INFO] [client] [118807] Using DNS servers: '172.17.0.1, '
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.558335+0000] [INFO] [libsdwan][118807] set_dns: 172.17.0.1
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.560115+0000] [INFO] [libsdwan][118807] sdwan_state: Offline None
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.560135+0000] [INFO] [client] [118807] State: 'Offline', client mode: 'None'
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.560203+0000] [INFO] [libsdwan][118807] sdwan_state: Authenticating None
Dec 06 16:04:24 fraruca twingated[118807]: [2023-12-06T16:04:24.560219+0000] [INFO] [client] [118807] State: 'Authenticating', client mode: 'None'

Can you run sudo twingate config log-level debug and then attemp t to start Twingate again and provide the updated output from the systemctl status twingate command

Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396569+0000] [WARNING] [libsdwan][26336] [controller] operator(): failed to get public keys: dns error: non-recoverable failure in name resolution,>
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396615+0000] [DEBUG] [libsdwan][26336] [controller] set_state: switching from “Getting public keys” to “Error”
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396663+0000] [INFO] [libsdwan][26336] sdwan_state: Error None
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396705+0000] [INFO] [client] [26336] State: ‘Error’, client mode: ‘None’
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396929+0000] [INFO] [client] [26336] Using DNS servers: '172.17.0.1, ’
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.396954+0000] [INFO] [libsdwan][26336] set_dns: 172.17.0.1
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.397063+0000] [DEBUG] [libsdwan][26336] __configure_sdwan_dns: added “172.17.0.1”
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.397195+0000] [DEBUG] [libsdwan][26336] configure_viper_dns: '{“modules”:{“viper”:{“dns-proxy”:{“bypass-dnsserver-map”:[{“from”:“100.95.0.251”,“to”:>
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.397248+0000] [DEBUG] [libsdwan][26336] sdwan_dns_set: DNS has been configured successfully
Dec 07 15:38:00 fraruca twingated[26336]: [2023-12-07T15:38:00.397314+0000] [DEBUG] [libsdwan][26336] [controller] run_state_machine: Error

So that looks like it’s having trouble resolving DNS. It appears to be trying to use 172.17.0.1 as the DNS server. Does that make sense? is that what you’d be expecting it to be using?