Stuck on trying server.. Retry.

[eddiewang]

Have the zen daemon completely setup and linked up.
However the zen-secnodetracker can't seem to connect to a ts1.eu / ts2.eu etc. server.

Using IPv6.

Secure node config found OK - linking...
Retrieving zen rpc config....
You setup ipv6 connectivity. We need to apply a workaround for dns resolution.
STARTING NODETRACKER
CPU Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz count=8 speed=3780
Node.js version: v8.12.0
Tracker app version: 0.3.1
Node type: secure
MemTotal: 32.03GB  MemFree: 21.91GB  MemAvailable: 29.93GB  SwapTotal: 16.37GB  SwapFree: 16.37GB
2018-11-21 20:30:23 UTC -- No connection to server ts1.eu. Retry.
2018-11-21 20:30:53 UTC -- No connection to server ts1.eu. Retry.
2018-11-21 20:31:23 UTC -- No connection to server ts1.eu. Retry.
2018-11-21 20:31:24 UTC -- Trying server: ts3.eu
2018-11-21 20:31:53 UTC -- No connection to server ts3.eu. Retry.
2018-11-21 20:32:23 UTC -- No connection to server ts3.eu. Retry.
2018-11-21 20:32:25 UTC -- Trying server: ts4.eu
2018-11-21 20:32:53 UTC -- No connection to server ts4.eu. Retry.

[eddiewang]

I've tracked this to the socket.io client timing out:

2018-11-21 21:44:43 UTC -- No connection to server ts1.eu. Retry.
connect error timeout
connect error timeout
2018-11-21 21:45:13 UTC -- No connection to server ts1.eu. Retry.
2018-11-21 21:45:14 UTC -- Trying server: ts3.eu
connect error timeout
2018-11-21 21:45:43 UTC -- No connection to server ts3.eu. Retry.
connect error timeout
2018-11-21 21:46:13 UTC -- No connection to server ts3.eu. Retry.
2018-11-21 21:46:15 UTC -- Trying server: ts4.eu
connect error timeout
2018-11-21 21:46:43 UTC -- No connection to server ts4.eu. Retry.
connect error timeout
2018-11-21 21:47:13 UTC -- No connection to server ts4.eu. Retry.
2018-11-21 21:47:16 UTC -- Trying server: ts4.na
connect error timeout
2018-11-21 21:47:43 UTC -- No connection to server ts4.na. Retry.

I logged this error out manually, but I still can't seem to figure out why there is a timeout that occurs. pinging those servers work fine from inside the docker container.