Channel_event: Failed to establish a relay channel with "ice://7517": 60 (Operation timed out)

Unable to resolve VPN services suddenly, this was prior to recent update. Same results after update…
Tried restarting machine several times, restarting Twingate and re-authenticating several times, tried Windows and Mac versions… verified DNS settings. Kind of running out of ideas.

Logs have some interesting entries:

2022-06-01 14:53:57.065 Twingate[2288:9701] VPN stop completed
2022-06-01 14:53:58.070 Twingate[2288:9701] Attempt to reconnect
2022-06-01 14:53:58.071 Twingate[2288:9701] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:] [Line 119] Starting VPN setup for connect
2022-06-01 14:53:58.071 Twingate[2288:9701] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:] [Line 134] Dispatching start command
2022-06-01 14:53:58.071 Twingate[2288:9925] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:]_block_invoke [Line 137] Executing start command
2022-06-01 14:53:58.072 Twingate[2288:9925] [TunnelSDK] -[VPNManager setVpnConfiguration:withConfigType:withCompletion:]_block_invoke [Line 542] Setting profile for CONNECT
2022-06-01 14:53:58.072 Twingate[2288:9925] [TunnelSDK] -[VPNManager setVpnConfiguration:withConfigType:withCompletion:]_block_invoke [Line 567] Saving profile
2022-06-01 14:53:58.085 Twingate[2288:9701] [TunnelSDK] -[VPNManager setVpnConfiguration:withConfigType:withCompletion:]_block_invoke_2 [Line 569] Saving profile finished saved with error (null)
2022-06-01 14:53:58.085 Twingate[2288:9701] [TunnelSDK] -[VPNManager loadVpnConfigurationWithCompletion:] [Line 496] Loading tunnel manager
2022-06-01 14:53:58.085 Twingate[2288:9701] [TunnelSDK] -[VPNManager loadVpnConfigurationWithCompletion:] [Line 498] Refresh existing manager
2022-06-01 14:53:58.085 Twingate[2288:9701] [TunnelSDK] -[VPNManager loadVpnConfigurationWithCompletion:]_block_invoke [Line 500] Refresh finished with error (null)
2022-06-01 14:53:58.086 Twingate[2288:9701] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:]_block_invoke [Line 161] Calling VPN start
2022-06-01 14:53:58.086 Twingate[2288:9701] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:]_block_invoke [Line 201] Start finished with success
2022-06-01 14:53:58.087 Twingate[2288:9925] [TunnelSDK] -[VPNManager startVPNWithConfiguration:completion:]_block_invoke_3 [Line 208] Start command finished executing
2022-06-01 14:53:58.089 Twingate[2288:9701] [TunnelSDK] -[VPNManager vpnStatusChanged:] [Line 411] VPN status changed 2
2022-06-01 14:53:58.375 Twingate[2288:9701] [TunnelSDK] -[VPNManager vpnStatusChanged:] [Line 411] VPN status changed 3
2022-06-01 14:53:58.432 Twingate[2288:9701] [TunnelSDK] -[VPNManager finishStartWithError:] [Line 371] Start finished with error (null)
2022-06-01 14:53:58.432 Twingate[2288:9701] VPN start completed


[2022-06-01 15:40:40.858526] relay_on_bev_event(0x7fa224b559a0) events: 40, state: 1
[2022-06-01 15:40:40.858548] relay_on_bev_event(0x7fa224b559a0) timeout
[2022-06-01 15:40:40.858579] relay_on_error(0x7fa224b559a0, :0->:0)
[2022-06-01 15:40:40.858585] relay_set_state(0x7fa224b3e320): switching state from 1 to 5
[2022-06-01 15:40:40.858620] channel_event: Failed to establish a relay channel with "ice://7517": 60 (Operation timed out)
[2022-06-01 15:40:40.858629] HYD: pool_up_async_connect_cb: conn destroyed while waiting to be connected?
[2022-06-01 15:40:40.858635] relay_remove_conntrack(0x7fa224b559a0)
[2022-06-01 15:40:40.858656] _relay_free(0x7fa224b559a0, :0->:0)
[2022-06-01 15:40:40.878166] sdwan_async_connect: connecting to "ice://7517"
[2022-06-01 15:40:40.878197] get_ct: token_fetcher: requesting ct_key_t(network: 7517)
[2022-06-01 15:40:40.878330] get_token: token_fetcher: got a cached token for ct_key_t(network: 7517)
[2022-06-01 15:40:40.878534] operator(): using address '35.245.248.228:30009'

Basically any time I try to hit any service in any of our kubernetes clusters, I get timeouts.
I haven’t ruled out issues in our load balancers, and no other users have reported this issue as of yet.

Hi @mpayne, it isn’t clear if this is a client or connector issue. In the first instance could you try running your connector in debug mode. Please see here for details: Troubleshooting