# Claimed nodes not reporting to Cloud **URL:** \ **Category:** Help\ **Tags:** cloud\ **Created:** [May 11, 2021, 5:58pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282 "2021-05-11T17:58:30Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![netdatauser](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/netdatauser/32/794_2.png) [@netdatauser](https://community.netdata.cloud/u/netdatauser)\ **Post date:** [May 11, 2021, 5:58pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/1 "2021-05-11T17:58:31Z")
I know that this problem has come up before, but I don’t see any solutions. I have many nodes, but 5 of them are not reporting. All 5 are on Ubuntu 18.04. I installed NetData via the kickstart script. I then claimed the nodes. They show up in the Cloud dashboard, but no stats are shown. When I hover my mouse over the node, it says: “The agent on this node has an older version and an update is required. Please upgrade to agent version v1.26 or above.” Well, all 5 of these nodes are above that: ```auto # netdata -V netdata v1.30.1-140-nightly ``` I tried re-installing netdata on one of these, but no luck. I also tried restarting the netdata service, but that didn’t work either. I have other Ubuntu 18.04 nodes that report to the cloud just fine. Also, directly visiting the dashboard on the node works just fine. ---
**Author:** ![George\_Koulogiannis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/george_koulogiannis/32/729_2.png) [@George\_Koulogiannis](https://community.netdata.cloud/u/George_Koulogiannis)\ **Post date:** [May 12, 2021, 7:51am UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/2 "2021-05-12T07:51:57Z")
Hello, We are investigating the issue, and we will revert back to you. ---
**Author:** ![underhood](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/underhood/32/798_2.png) [@underhood](https://community.netdata.cloud/u/underhood)\ **Post date:** [May 12, 2021, 9:35am UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/3 "2021-05-12T09:35:53Z")
@netdatauser can you take a look at: - what does error log say if you filter it for `aclk` keyword (`grep -ai aclk error.log`)? - What does `netdata -W buildinfo` say? ---
**Author:** ![netdatauser](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/netdatauser/32/794_2.png) [@netdatauser](https://community.netdata.cloud/u/netdatauser)\ **Post date:** [May 12, 2021, 4:57pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/4 "2021-05-12T16:57:29Z")
Thanks for the quick response! > what does error log say if you filter it for `aclk` keyword ( `grep -ai aclk error.log` )? Looks like this is repeating in the log: ```auto 2021-05-12 09:27:55: netdata ERROR : ACLK_Main : Challenge failed: 2021-05-12 09:27:55: netdata INFO : ACLK_Main : Retrying to establish the ACLK connection in 1024.000 seconds 2021-05-12 09:44:59: netdata INFO : ACLK_Main : Attempting to establish the agent cloud link 2021-05-12 09:44:59: netdata INFO : ACLK_Main : Retrieving challenge from cloud: app.netdata.cloud 443 /api/v1/auth/node//challenge 2021-05-12 09:44:59: netdata INFO : ACLK_Main : aclk_send_https_request GET 2021-05-12 09:44:59: netdata ERROR : ACLK_Main : Libwebsockets: SSL error: unable to get local issuer certificate (preverify_ok=0;err=20;depth=1) ``` > What does `netdata -W buildinfo` say? Here is the output: ```auto Version: netdata v1.30.1-142-nightly Configure options: '--prefix=/usr' '--sysconfdir=/etc' '--localstatedir=/var' '--libexecdir=/usr/libexec' '--libdir=/usr/lib' '--with-zlib' '--with-math' '--with-user=netdata' '--with-bundled-lws=externaldeps/libwebsockets' 'CFLAGS=-O2' 'LDFLAGS=' Features: dbengine: YES Native HTTPS: YES Netdata Cloud: YES Cloud Implementation: Legacy TLS Host Verification: YES Libraries: jemalloc: NO JSON-C: YES libcap: NO libcrypto: YES libm: YES LWS: YES static v3.2.2 mosquitto: YES tcalloc: NO zlib: YES Plugins: apps: YES cgroup Network Tracking: YES CUPS: NO EBPF: YES IPMI: NO NFACCT: NO perf: YES slabinfo: YES Xen: NO Xen VBD Error Tracking: NO Exporters: AWS Kinesis: NO GCP PubSub: NO MongoDB: NO Prometheus Remote Write: NO ``` It seems like maybe “_Libwebsockets: SSL error: unable to get local issuer certificate_” is the problem? Not sure what that is looking for exactly though. ---
**Author:** ![underhood](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/underhood/32/798_2.png) [@underhood](https://community.netdata.cloud/u/underhood)\ **Post date:** [May 12, 2021, 6:03pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/5 "2021-05-12T18:03:02Z")
Yes it indeed looks like certificate verification is the problem for some reason. app.netdata.cloud uses Let’s Encrypt certificate. I will install VM with Ubuntu 18.04 tomorrow (probably) to see if I can reproduce the issue. @Austin_Hemmelgarn I remember we had long time ago issues with certificate verification on some systems but can’t quite recall what it was. Do you remember? ---
**Author:** ![Austin\_Hemmelgarn](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/austin_hemmelgarn/32/4495_2.png) [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)\ **Post date:** [May 12, 2021, 6:28pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/6 "2021-05-12T18:28:12Z")
Yes, we had some issues at one point, but it was never on Ubuntu. The only things that should cause this kind of error on Ubuntu are either not having the `ca-certificates` package installed or using a very atypical OpenSSL client configuration. ---
**Author:** ![netdatauser](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/netdatauser/32/794_2.png) [@netdatauser](https://community.netdata.cloud/u/netdatauser)\ **Post date:** [May 12, 2021, 9:11pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/7 "2021-05-12T21:11:57Z")
Something is odd about the ca-certificates on these specific hosts. I do have other Ubuntu 18.04 servers that work fine. Using `update-ca-certificates` has some errors about newlines, and so some of the ca certs aren’t being linked. I’ll have to see if I can resolve that. ---
**Author:** ![netdatauser](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/netdatauser/32/794_2.png) [@netdatauser](https://community.netdata.cloud/u/netdatauser)\ **Post date:** [May 14, 2021, 8:12pm UTC](https://community.netdata.cloud/t/claimed-nodes-not-reporting-to-cloud/1282/8 "2021-05-14T20:12:47Z")
I found a script mistakenly named `test` in the `$PATH` that was related to some internal tools. This caused the `update-ca-certificates` to not complete properly as it was using the wrong test. As a result, there was missing root certs in the generated file(s). Thanks for helping me find the errors in the log. That really got me going in the right direction.