Claim not working on Ubuntu 24 LTS + Docker. SSL connect error.

Help
,
1

I had to reinstall Ubuntu (24.04.4 LTS aarch64) on my four cluster nodes. When trying to restart Netdata in a Docker (29.5.2) container /* I used the example command from your website */, I came to the point where the Netdata dashboards of all four nodes worked. What did not work, though, was claiming them in the cloud dashboard. I used the corresponding token I read from:

docker exec netdata cat /var/lib/netdata/netdata_random_session_id

Alas, on all four nodes, I got this error message:

Request failed with error: SSL connect error
proxy: 'env',
insecure: false,
public key file: '/var/lib/netdata/cloud.d/public.pem',
trusted key file: 'none'

Yes, I do have a firewall with HTTP/HTTPS proxy sitting between the nodes and the rest of my network, but is this the cause why the SSL connection breaks? Or does it have to do with the non-standard TCP ports (19995 thru 19998, one for each node) I have to use because of the firewall? Last time, the claim worked flawlessly!

I also executed this command, but no use:

sudo apt-get install --reinstall ca-certificates
2

Yes, your proxy is almost certainly the cause.

The proxy: 'env' in the error means Netdata is looking for proxy settings in environment variables but either they’re not set inside the container, or the proxy is intercepting the SSL connection and presenting its own certificate which Netdata rejects.

The cleanest fix for Docker is to pass the proxy when starting the container using the NETDATA_CLAIM_PROXY environment variable:

docker run -d \
  --name netdata \
  -e NETDATA_CLAIM_TOKEN=YOUR_TOKEN \
  -e NETDATA_CLAIM_ROOMS=YOUR_ROOM_IDS \
  -e NETDATA_CLAIM_PROXY=http://your-proxy-host:your-proxy-port \
  ... (rest of your existing flags)
  netdata/netdata

Alternatively, claim manually from inside the container:

docker exec netdata netdata-claim.sh \
  -token=YOUR_TOKEN \
  -rooms=YOUR_ROOM_IDS \
  -url=https://app.netdata.cloud \
  -proxy=http://your-proxy-host:your-proxy-port

First, verify the proxy can reach Netdata Cloud from inside the container:

docker exec netdata curl -v --proxy http://your-proxy-host:port https://app.netdata.cloud

If that fails, the proxy is blocking or intercepting the connection. Make sure it allows outbound connections to app.netdata.cloud:443 and mqtt.netdata.cloud:443.

The non-standard ports (19995-19998) won’t affect claiming.