Niko
Niko
I also encounter this issue. ## Environment and versions * OS: Debian GNU/Linux 12 (bookworm) x86_64 * Version: 2023.8.2 (built 2023-08-31-1506 UTC) ``` 2023-09-12T13:35:02Z INF Starting tunnel tunnelID=f6a0bf44-b65e-4dd2-bd0e-666ed08e9c6a 2023-09-12T13:35:02Z INF...
It seems this issue can be solved by parsing the `argotunnel.com` domain to A type not AAAA. After I forced the `argotunnel.com` with A type during DNS resolve, the tunnel...
> I'm receiving the same issue as OP, @NikoTung can you explain how you resolved this with "After I forced the argotunnel.com with A type during DNS resolve" - thanks...