[Bug]: Netdata Cloud isn't reachable via IPv6

[ghost]

Bug description

It's impossible to reach Netdata Cloud without IPv4 (IPv6 only).

Expected behavior

Netdata Cloud should be reachable on IPv6 only environments.

Steps to reproduce

1. Install Netdata Agent on an IPv6 only machine
2. Get errors
3. Your server don't show up on app.netdata.cloud

Screenshots

No response

Error Logs

--- Attempting to claim agent to https://app.netdata.cloud --- 2319957 2319965 [/tmp/netdata-kickstart-lPxi5C5oPs]# /usr/sbin/netdata-claim.sh -token=REDACTED -rooms=REDACTED -url=https://app.netdata.cloud Token: **************** Base URL: https://app.netdata.cloud Id: REDACTED Rooms: REDACTED Hostname: REDACTED Proxy: Netdata user: netdata Failed to connect to https://app.netdata.cloud, return code 7 Connection attempt 1 failed. Retry in 1s. Failed to connect to https://app.netdata.cloud, return code 7 Connection attempt 2 failed. Retry in 2s. Failed to connect to https://app.netdata.cloud, return code 7 Connection attempt 3 failed. Retry in 3s. grep: /var/lib/netdata/cloud.d/tmpout.txt: No such file or directory grep: /var/lib/netdata/cloud.d/tmpout.txt: No such file or directory Failed to claim node with the following error message:"Unknown HTTP error message" FAILED

Command "/usr/sbin/netdata-claim.sh -token=SCVKb0zJ3vnSHef97dHQ3Wa-6QieWsJ9mKY5OcyMUAal-LTcemSPXQW0qpzuOgsGfqX08JSZwZOH5RaI3fRACVYDXkYyy-Z__Gac4zubIGNdd7r4WraA3HMGwjbe8BLGGDUPyVI -rooms=6a455b44-4a04-4ba6-876e-3823df1ce747 -url=https://app.netdata.cloud" failed with exit code 7.

% dig -t AAAA app.netdata.cloud main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com.

Desktop

Doesn't matter.

Additional context

Thanks in advance for your help! Would love to subscribe to a paid plan but can't do so if my IPv6 only servers can't be added. :)

[hugovalente-pm]

@netdata/cloud-sre could you help on this one?

[hugovalente-pm]

@mthld I've checked this internally and it is something we have identified that we want want to sort out but due to other priorities we haven't been able to tackle it yet.

[ghost]

Thanks for the feedback! Hope you'll manage to sort this out at some point. I'll check back your service when this issue gets fixed. 🙌🏻

[tiagogaspar8]

Why was this closed? Should I create a new one?

[hugovalente-pm]

@tiagogaspar8 not sure, it is still on our plans to tackle this so will reopen the issue