If I access the IP address of the node through the Netdata port the panel appears perfectly and monitors successfully, but, when I access from Netdata cloud (https://app.netdata.cloud), the node appears unreachable.
My setup is Linux (Ubuntu Server 18.04 LTS)
The error that was displayed when I ran the installation script (kickstart) is “already claimed”
So I run the claim script to claim the node
sudo ./[netdata-claim.sh](http://netdata-claim.sh/) -token=<Token> -id=$(uuidgen) -rooms=<Room ID> -url=[https://app.netdata.cloud](https://app.netdata.cloud/)
It seems to work locally, in the panel now appears the node, but, it appears as unreachable on the Cloud.
Is it possible to get
netdata -W buildinfo ,
netdatacli aclk-state and
grep -i ACLK error.log
netdata -W buildinfo
Version: netdata v1.32.1-30-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’ ‘–with-bundled-protobuf’ ‘CFLAGS=-O2’ ‘LDFLAGS=’
Native HTTPS: YES
Netdata Cloud: YES
ACLK Next Generation: YES
ACLK-NG New Cloud Protocol: YES
ACLK Legacy: YES
TLS Host Verification: YES
Machine Learning: YES
protobuf: YES (bundled)
LWS: YES static v3.2.2
cgroup Network Tracking: YES
Xen VBD Error Tracking: NO
AWS Kinesis: NO
GCP PubSub: NO
Prometheus Remote Write: NO
ACLK Available: Yes
ACLK Implementation: Next Generation
New Cloud Protocol Support: Yes
Claimed Id: 697c2a92-b4e0-46f9-8c26-129ea256b2c3
Used Cloud Protocol: Legacy
The last thing you asked me, I don’t know how to give it to you. If you indicate the command in detail, I will gladly provide you with the requested information.
@iLxlo Thank you
grep -i ACLK /var/log/netdata/error.log.
netdatacli aclk-state output it seems agent believes it is connected to cloud. @papazach can we search this agent on VerneMQ by claim id above?
@iLxlo thank you. From the log, it seems to me the agent is indeed successfully connected to the cloud. I am asking around our cloud devs to take a look (why it appears offline in the cloud dashboard).
Hi @iLxlo !
The agent looks to be online from the cloud, however it does not appear to belong to any room. Could you check the nodes available for the room you want and try adding this one?
Instructions on that can be found here: War Rooms | Learn Netdata.
Done. It seems that the problem was more derived from the nodes that appear in the list of available nodes.
Apparently I had duplicated the same node x10 times, 7 of them were listed as “Available” (they did not have the unreachable mark). I have added all the nodes that were available and finally I have found the node that belongs to me.
The remainder were assigned the “unreachable” mark.
Thanks for your help and now you can close this thread!
Really happy to hear you now have access to your node @iLxlo !
Let us know if you need any further help and we’ll be happy to assist!