netdata-agend installation: aclk-available

Help
1

Hi,

I´m a Netdata cloud business customer. Currently I am trying to install the netdata-agend on mutliple Servers.

This worked well on two servers. On the third, I ran the netdata installer as on the others and linked it using token and roomid. The service is running, but I don’t see it in my active nodes, neither online nor offline. So far, I’ve only noticed one difference in the server configuration: `aclk-available` is set to false. What could be the cause of this, and how do I fix it? I performed the installation process identically on all servers.

Thanks and best regards

Joshua

2

Hello,

The aclk_online() function returns the current state of the WebSocket connection to Netdata Cloud. When it’s false, it means the Agent cannot establish a connection to Netdata Cloud, even though the claiming process may have succeeded.

This could be caused by a multitude of reasons. To help us correctly diagnose the issue, please run these commands on the problematic server:

1. Check Detailed ACLK State

sudo netdatacli aclk-state

This will show us the exact connection status and any error messages.

2. Check Agent Info API

Visit http://YOUR_SERVER_IP:19999/api/v3/info and look at the cloud section for diagnostic information.

3. Check Netdata Logs

# Linux with systemd
sudo journalctl -u netdata --namespace netdata -xe | grep -i aclk

# Linux without systemd
sudo cat /var/log/netdata/daemon.log | grep -i aclk

Look for “CLAIM” related messages to see why the connection failed.

3

Hi,

thanks for your answer.

ACLK-STATE:

ACLK Available: Yes
ACLK Version: 2
Protocols Supported: Protobuf
Protocol Used: Protobuf
MQTT Version: 5
Claimed: Yes
Claimed Id: XXX (seems correct)
Cloud URL: https://app.netdata.cloud
ACLK Proxy: none
Publish Latency: off
Online: No
Reconnect count: 0
Banned By Cloud: No
Next Connection Attempt At: 2026-04-05 14:11:49

Agent Info API:

                   "cloud":  {
                                 "id":  0,
                                 "status":  "offline",
                                 "since":  1772797723,
                                 "age":  11075,
                                 "claim_id":  XXX (same ID as above),
                                 "url":  "https://app.netdata.cloud",
                                 "reason":  "/env response code is not 200",
                                 "next_check":  1775391109,
                                 "next_in":  2582311

Netdata Logs:

I can’t find any logs under /var/log/netdata/

I can just see a service.log which shows the windows Service getting started.

I tried several reinstallations to reestablish the connection, but it didn’t work.

Thanks and Best Regards

Joshua

4

Hi Joshua,

Thank you for the detailed output.

The error /env response code is not 200 means your agent is reaching Netdata Cloud but the connection is being rejected during the initial handshake. This is almost always a network-level issue specific to this server — firewall rules, a proxy, or TLS configuration that differs from your other two servers.

One important thing to note first: your agent’s next connection attempt is scheduled far in the future due to a backoff from repeated failures. Once you’ve resolved the underlying issue, please restart the Netdata service to force an immediate reconnect:

Restart-Service Netdata

Please work through the following steps:

Step 1: Test connectivity to Netdata Cloud

Run these in PowerShell to confirm the server can reach our infrastructure:

# Test DNS resolution
Resolve-DnsName "app.netdata.cloud"

# Test HTTPS connectivity
Invoke-WebRequest -Uri "https://app.netdata.cloud" -Method HEAD -UseBasicParsing

# Test the specific endpoint the agent uses
Invoke-WebRequest -Uri "https://app.netdata.cloud/api/v1/env" -Method GET -UseBasicParsing

If any of these fail, the issue is network or firewall related.

Step 2: Check firewall rules

Ensure outbound traffic is allowed to app.netdata.cloud on port 443. Check whether this server has any firewall rules or security policies that differ from your other two servers.

Step 3: Check for a proxy

If this server sits behind a corporate proxy, Netdata needs to be configured to use it. Add the following to C:\Program Files\Netdata\etc\netdata\claim.conf:

[global]
    proxy = http://your-proxy-address:port

Step 4: Verify TLS configuration

Older Windows configurations may have TLS 1.2 disabled. Check your current TLS settings:

[System.Net.ServicePointManager]::SecurityProtocol

If TLS 1.2 is not listed, it will need to be enabled at the OS level.

Step 5: Check Netdata logs

To see what Netdata log channels are available on your system and check for relevant errors:

Get-WinEvent -ListLog "*Netdata*" -ErrorAction SilentlyContinue

Please start with Step 1 and share the output. It will tell us immediately whether this is a connectivity or configuration issue.

Kind Regards,
Kanela

5

Hi Kanela,

i tryed your steps:

Step 1:

DNS:

Name                                           Type   TTL   Section    IPAddress

app.netdata.cloud                              AAAA   300   Answer     2606:4700:10::ac42:aad8
app.netdata.cloud                              AAAA   300   Answer     2606:4700:10::6814:1602
app.netdata.cloud                              A      300   Answer     104.20.22.2
app.netdata.cloud                              A      300   Answer     172.66.170.216

HTTPS:

StatusCode : 200
StatusDescription : OK
Content :
RawContent : HTTP/1.1 200 OK
Connection: keep-alive
access-control-allow-credentials: true
Server-Timing: cfCacheStatus;desc=“DYNAMIC”,cfEdge;dur=5,cfOrigin;dur=82
x-content-type-options: nosniff
x-frame-opti…
Forms :
Headers : {[Connection, keep-alive], [access-control-allow-credentials, true], [Server-Timing,
cfCacheStatus;desc=“DYNAMIC”,cfEdge;dur=5,cfOrigin;dur=82], [x-content-type-options, nosniff]…}
Images : {}
InputFields : {}
Links : {}
ParsedHtml :
RawContentLength : 0

Endpoint Test:

I receive an error: {“errorCode”:“dFLf2q4g4x-6441850”,“errorMsgKey”:“ErrInvalidClaimID”,“errorMessage”:“claim_id not a
valid UUID”,“errorRetryDelaySeconds”:2592000}

If i try it with the claimed_id from the cloud.d folder (https://app.netdata.cloud/api/v1/env?claim_id=XX) i get another error: {“errorCode”:“zkxmdeEYsK-6450361”,“errorMsgKey”:“ErrUnsupportedAgent”,“errorMessage”:“do not
retry: unsupported agent”,“errorRetryDelaySeconds”:2592000}

I couldnt find any proxy or TLS configuration problems.

Netdata Logs:

LogMode   MaximumSizeInBytes RecordCount LogName
-------   ------------------ ----------- -------
Circular             1052672         116 Netdata/Access
Circular             1052672           0 Netdata/Aclk
Circular             1052672         615 Netdata/Collectors
Circular             1052672         821 Netdata/Daemon
Circular             1052672          64 Netdata/Health

I still cant find any usefull log files. Is this normal?

Verzeichnis: C:\Program Files\Netdata\var\log\netdata

Mode                LastWriteTime         Length Name




-a----       15.03.2026     16:11              0 aclk.log
-a----       15.03.2026     16:11            302 service.log

Do the errors tell you whats wrong here?

Thanks and Kind Regards,

Joshua

6

Hi Joshua,

Thank you for running those tests and for providing the output.

The ErrInvalidClaimID error suggests there may be an issue with the claim_id in your configuration file. Could you please share the contents of your claim.conf file? You can find it at:

C:\Program Files\Netdata\etc\netdata\claim.conf

Additionally, could you share the logs from Windows Event Viewer? First, list the available Netdata log channels:

wevtutil el | Select-String "Netdata"

Then retrieve the logs from the most relevant channels for this issue:

Get-WinEvent -LogName "Netdata/Daemon" -MaxEvents 100
Get-WinEvent -LogName "Netdata/Aclk" -MaxEvents 100

This should help us understand what’s happening on your system.

Kind Regards,
Kanela

7

Hi Kanela,

thanks for the quick response!

claim.conf:
[global]
url = https://app.netdata.cloud
token = XX (135 characters)
rooms = XX (36 characters)

#proxy =

insecure = no

Here are the last 100 log-entrys:

daemon:


TimeCreated      : 16.03.2026 13:59:16
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[48]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000075.njfv2", file size 1565448 bytes (1.49MiB)

TimeCreated      : 16.03.2026 13:59:16
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[48]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000075.njfv2":
                   extents 247, metrics 4372, pages 26923

TimeCreated      : 16.03.2026 13:59:16
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[48]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000075.njf" is ready
                   to be indexed

TimeCreated      : 16.03.2026 13:59:16
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[27]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000076.njf".

TimeCreated      : 16.03.2026 13:59:16
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[27]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000076.ndf".

TimeCreated      : 16.03.2026 11:11:42
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000074.njfv2", file size 1537456 bytes (1.47MiB)

TimeCreated      : 16.03.2026 11:11:42
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000074.njfv2":
                   extents 243, metrics 4226, pages 26487

TimeCreated      : 16.03.2026 11:11:41
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000074.njf" is ready
                   to be indexed

TimeCreated      : 16.03.2026 11:11:41
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[33]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000075.njf".

TimeCreated      : 16.03.2026 11:11:41
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[33]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000075.ndf".

TimeCreated      : 16.03.2026 10:42:14
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine-tier1/journalfile-1-0000000010.njfv2", file size 3064724 bytes (2.92MiB)

TimeCreated      : 16.03.2026 10:42:14
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: indexing file
                   "/var/cache/netdata/dbengine-tier1/journalfile-1-0000000010.njfv2": extents 512, metrics 4178, pages 55808

TimeCreated      : 16.03.2026 10:42:13
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: journal file "/var/cache/netdata/dbengine-tier1/journalfile-1-0000000010.njf" is
                   ready to be indexed

TimeCreated      : 16.03.2026 10:42:13
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[46]): DBENGINE: created journal file
                   "/var/cache/netdata/dbengine-tier1/journalfile-1-0000000011.njf".

TimeCreated      : 16.03.2026 10:42:13
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[46]): DBENGINE: created data file "/var/cache/netdata/dbengine-tier1/datafile-1-0000000011.ndf".

TimeCreated      : 16.03.2026 08:23:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[18]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000073.njfv2", file size 1479820 bytes (1.41MiB)

TimeCreated      : 16.03.2026 08:23:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[18]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000073.njfv2":
                   extents 234, metrics 4046, pages 25506

TimeCreated      : 16.03.2026 08:23:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[18]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000073.njf" is ready
                   to be indexed

TimeCreated      : 16.03.2026 08:23:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[44]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000074.njf".

TimeCreated      : 16.03.2026 08:23:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[44]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000074.ndf".

TimeCreated      : 16.03.2026 05:20:08
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[14]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000072.njfv2", file size 1548164 bytes (1.48MiB)

TimeCreated      : 16.03.2026 05:20:07
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[14]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000072.njfv2":
                   extents 248, metrics 3734, pages 27032

TimeCreated      : 16.03.2026 05:20:07
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[14]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000072.njf" is ready
                   to be indexed

TimeCreated      : 16.03.2026 05:20:07
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[21]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000073.njf".

TimeCreated      : 16.03.2026 05:20:07
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[21]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000073.ndf".

TimeCreated      : 16.03.2026 02:00:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[33]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000071.njfv2", file size 1500964 bytes (1.43MiB)

TimeCreated      : 16.03.2026 02:00:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[33]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000071.njfv2":
                   extents 240, metrics 3686, pages 26160

TimeCreated      : 16.03.2026 02:00:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[33]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000071.njf" is ready
                   to be indexed

TimeCreated      : 16.03.2026 02:00:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[15]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000072.njf".

TimeCreated      : 16.03.2026 02:00:02
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[15]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000072.ndf".

TimeCreated      : 15.03.2026 22:46:12
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000070.njfv2", file size 1519308 bytes (1.45MiB)

TimeCreated      : 15.03.2026 22:46:12
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000070.njfv2":
                   extents 244, metrics 3564, pages 26596

TimeCreated      : 15.03.2026 22:46:12
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000070.njf" is ready
                   to be indexed

TimeCreated      : 15.03.2026 22:46:12
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[32]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000071.njf".

TimeCreated      : 15.03.2026 22:46:12
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[32]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000071.ndf".

TimeCreated      : 15.03.2026 19:27:23
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[40]): DBENGINE: migrated journal file
                   "/var/cache/netdata/dbengine/journalfile-1-0000000069.njfv2", file size 1416948 bytes (1.35MiB)

TimeCreated      : 15.03.2026 19:27:23
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[40]): DBENGINE: indexing file "/var/cache/netdata/dbengine/journalfile-1-0000000069.njfv2":
                   extents 229, metrics 3089, pages 24961

TimeCreated      : 15.03.2026 19:27:23
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[40]): DBENGINE: journal file "/var/cache/netdata/dbengine/journalfile-1-0000000069.njf" is ready
                   to be indexed

TimeCreated      : 15.03.2026 19:27:23
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[28]): DBENGINE: created journal file "/var/cache/netdata/dbengine/journalfile-1-0000000070.njf".

TimeCreated      : 15.03.2026 19:27:23
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[28]): DBENGINE: created data file "/var/cache/netdata/dbengine/datafile-1-0000000070.ndf".

TimeCreated      : 15.03.2026 17:41:56
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[26]): Chart label metadata check completed

TimeCreated      : 15.03.2026 16:43:10
LevelDisplayName : Informationen
Message          : netdata(sensors_upd): heartbeat clock: woke up 77 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:42:52
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 78 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:42:48
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[3]): Chart metadata check completed

TimeCreated      : 15.03.2026 16:42:42
LevelDisplayName : Informationen
Message          : netdata(UV_WORKER[22]): Dimension metadata check completed

TimeCreated      : 15.03.2026 16:42:38
LevelDisplayName : Informationen
Message          : netdata(WIN_PLUGIN[18): heartbeat clock: woke up 77 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:42:29
LevelDisplayName : Informationen
Message          : netdata(WIN_PLUGIN[17): heartbeat clock: woke up 206 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:42:16
LevelDisplayName : Informationen
Message          : netdata(sensors_upd): heartbeat clock: woke up 238 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:42:05
LevelDisplayName : Informationen
Message          : netdata(PREDICT): heartbeat clock: woke up 384 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:41:55
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 171 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:41:46
LevelDisplayName : Informationen
Message          : netdata(WIN_PLUGIN[17): heartbeat clock: woke up 677 microseconds earlier than expected (can be due to the
                   CLOCK_REALTIME set to the past).

TimeCreated      : 15.03.2026 16:41:35
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 536 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:41:25
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 439 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:41:15
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 496 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:41:05
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 964 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:40:55
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 1722 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:40:45
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 1696 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:40:35
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 2321 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:40:25
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 2395 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:40:15
LevelDisplayName : Informationen
Message          : netdata(PULSE): heartbeat clock: woke up 272 microseconds earlier than expected (can be due to the CLOCK_REALTIME
                   set to the past).

TimeCreated      : 15.03.2026 16:32:01
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): Netdata Cloud, ACLK connection status: /env response code is not 200

TimeCreated      : 15.03.2026 16:32:01
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: Cloud returned EC="zkxmdeEYsK-5542734", Msg-Key:"ErrTooManyRequests",
                   Msg:"ErrTooManyRequests", BlockRetry:false, Backoff:2592000s (-1 unset by cloud)

                      Unix Errno   : 2, No such file or directory
                      Windows Error:


TimeCreated      : 15.03.2026 16:32:01
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: failed to get ACLK environment (ENV response code is not 200) (got 429)

TimeCreated      : 15.03.2026 16:32:01
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: HTTPS "GET" request to "app.netdata.cloud" finished with HTTP code: 429

TimeCreated      : 15.03.2026 16:32:01
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to app.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error passing Challenge/Response to get OTP

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): Netdata Cloud, ACLK connection status: https client failed to write http header

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error getting challenge

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: OTP Challenge failed

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't process request

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't write HTTP request header into SSL connection

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: SSL_write Err: SSL_ERROR_SSL

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): SSL: certificate verify error 19:self-signed certificate in certificate chain at depth 2,
                   subject: DC = INT, DC = BAG, CN = BAG-PKI-CA

                      Unix Errno   : 2, No such file or directory
                      Windows Error:


TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to api.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:32:00
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: HTTPS "GET" request to "app.netdata.cloud" finished with HTTP code: 200

TimeCreated      : 15.03.2026 16:31:59
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to app.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error passing Challenge/Response to get OTP

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): Netdata Cloud, ACLK connection status: https client failed to write http header

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error getting challenge

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: OTP Challenge failed

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't process request

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't write HTTP request header into SSL connection

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: SSL_write Err: SSL_ERROR_SSL

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): SSL: certificate verify error 19:self-signed certificate in certificate chain at depth 2,
                   subject: DC = INT, DC = BAG, CN = BAG-PKI-CA

                      Unix Errno   : 2, No such file or directory
                      Windows Error:


TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to api.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: HTTPS "GET" request to "app.netdata.cloud" finished with HTTP code: 200

TimeCreated      : 15.03.2026 16:31:58
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to app.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error passing Challenge/Response to get OTP

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): Netdata Cloud, ACLK connection status: https client failed to write http header

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error getting challenge

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: OTP Challenge failed

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't process request

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: couldn't write HTTP request header into SSL connection

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: SSL_write Err: SSL_ERROR_SSL

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): SSL: certificate verify error 19:self-signed certificate in certificate chain at depth 2,
                   subject: DC = INT, DC = BAG, CN = BAG-PKI-CA

                      Unix Errno   : 2, No such file or directory
                      Windows Error:


TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to api.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:31:57
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: HTTPS "GET" request to "app.netdata.cloud" finished with HTTP code: 200

TimeCreated      : 15.03.2026 16:31:56
LevelDisplayName : Informationen
Message          : netdata(ACLK_MAIN): ACLK: Connecting to app.netdata.cloud:443 (no proxy)

TimeCreated      : 15.03.2026 16:31:55
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): ACLK: error passing Challenge/Response to get OTP

TimeCreated      : 15.03.2026 16:31:55
LevelDisplayName : Fehler
Message          : netdata(ACLK_MAIN): Netdata Cloud, ACLK connection status: https client failed to write http header

The aclk-log seems to be empty.

Kinde Regards,

Joshua

8

Hi Joshua,

Thank you for sharing the logs and your claim.conf.

There are two issues at play:

1. SSL certificate verification failure

Your logs show:

SSL: certificate verify error 19: self-signed certificate in certificate chain at depth 2,
subject: DC = INT, DC = BAG, CN = BAG-PKI-CA

Your network has a corporate Certificate Authority (BAG-PKI-CA) performing SSL inspection on outbound connections. The Netdata Agent cannot validate this certificate because it’s not in the standard trusted root store, causing the ACLK connection to fail.

2. Rate limiting (HTTP 429)

The repeated failed connection attempts have triggered a 30-day rate limit backoff on Netdata Cloud. This is why the Next Connection Attempt At is set so far in the future. Restarting the Netdata service after fixing the SSL issue will reset this.

Here are your options, in order of preference:

Option 1: Install the corporate CA certificate (recommended)

Obtain the BAG-PKI-CA certificate from your IT department and import it into the Windows trusted root store:

certutil -addstore "Root" path\to\corporate_ca_cert.cer

Then restart the Netdata service.

Option 2: Configure a corporate proxy

If your organisation routes outbound traffic through a proxy, add it to C:\Program Files\Netdata\etc\netdata\claim.conf:

[global]
    url = https://app.netdata.cloud
    token = YOUR_TOKEN
    rooms = YOUR_ROOM
    proxy = http://proxy.yourcompany.com:8080
    insecure = no

Then restart the Netdata service.

Option 3: Disable SSL verification (last resort only)

If neither option above is possible, you can bypass SSL verification by setting insecure = yes in your claim.conf. This is not recommended as it reduces connection security, but can be used as a temporary measure.

After applying any of the above, restart the Netdata service to clear the rate limit backoff:

net stop Netdata && net start Netdata

Then verify the connection status:

netdatacli aclk-state

Kind Regards,
Kanela

9

Hi Kanela,

Step 1 worked for me.

Thank you!

Kind Regards,

Joshua

1 Like