Cant connect to Netdata cloud with claim token added.

[ahmedelakkad]

I added the claim token and room in the config and it wont add the node. Also, I cant sign in from netdata in HA it redirects to the sign in page and then says forbidden, contact your admin to access this node.

Here is the log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:49:59] INFO: Configuring Netdata...
2022-07-01 15:50:01: netdata INFO : MAIN : CONFIG: cannot load cloud config '/opt/netdata/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
2022-07-01 15:50:01: netdata INFO : MAIN : Found 0 legacy dbengines, setting multidb diskspace to 256MB
2022-07-01 15:50:01: netdata INFO : MAIN : Created file '/opt/netdata/var/lib/netdata/dbengine_multihost_size' to store the computed value
[15:50:05] INFO: Netdata configuration: set hostname to homeassistant
[15:50:06] INFO: Netdata configuration: set page_cache_size to 32
[15:50:06] INFO: Netdata configuration: set page_cache_size to 256
[15:50:06] INFO: Claiming agent to Netdata cloud... (may take a few seconds to show up in https://app.netdata.cloud)
[15:50:06] INFO: Starting Netdata...
--- Using /tmp/netdata-kickstart-XXXXHCGmAO as a temporary directory. ---
--- Checking for existing installations of Netdata... ---
--- Found an existing netdata install at /opt/netdata, with installation type 'kickstart-static'. ---
[/tmp/netdata-kickstart-XXXXHCGmAO]# /opt/netdata/usr/libexec/netdata/netdata-updater.sh --non-interactive --not-running-from-cron

[Gamma-Software]

Hey @ahmedelakkad !
I’m working on a better installation of Netdata using its base docker image. It’ll surely fix the issue. I keep you updated

[ahmedelakkad]

@Gamma-Software really appreciate your work!

[Gamma-Software]

Don’t close the issue. It’ll be closed after the fix. It’s not done yet :D

[ahmedelakkad]

@Gamma-Software ok my bad 😂

[mx2k]

I can see the same issue after not being able to claim via claim token from the .yaml config. When accessing netdata locally from the HA sidebar, it states not connected to cloud, offering the "connect to cloud now" button. the OPs described timeout also happens for me. Not sure if it was supposed to be fixed yet, but I can confirm it's still not really working. Also see my separate issue regarding claiming with spaces in room names.

[lakkeri]

Reason for "forbidden" message from netdata cloud is add-on running in ingress mode. Netdata forbids signing in from nodes running not in dedicated browser window.
Workaround for now: after unsuccessful connect attempt there is an offline node in "last visited nodes", there is a direct link you can use to open add-on in separate window and sign in from there.