Hey,
Would it be possible to send more info about your error? The terminal output when running it, what Agent version you are using, OS, etc.
It will greatly help us in understanding the root cause and troubleshoot it 
P.S Welcome to our community!
Perhaps it is curl exit code
CURLE_OPERATION_TIMEDOUT (28)
Operation timeout. The specified time-out period was reached according to the conditions.
I guess you get this message
Failed to connect to ${URL_BASE}, return code ${URLCOMMAND_EXIT_CODE}
am i right @Stavro_Purdie
No sorry its not that
It’s an error when i try to claim a node
Hello??
Can I please get a conformation about the issue
It seems https://app.netdata.cloud is no accesible for you 
Lets see, do and show the output of
curl -s -o /dev/null -w "%{http_code}\n" https://app.netdata.cloud; echo $?
It hasn’t really done anything
@Austin_Hemmelgarn any ideas?
It’s definitely cURL running into a timeout condition. Exit code 28 means that it successfully connected, but the actual HTTP request itself timed out (usually this translates to not getting any actual response). Unfortunately it’s rather difficult to diagnose things much further than that. We probably would need to get the cloud team to look for any error logs related to the claiming endpoint, because such a failure should show up there (at minimum as an unexpectedly closed connection).
So do you want me to run any commands …. Some people think that you could delete something or edit a file to make the timeout time longer.
I know how to do it its just i dont know the files
Found the issue cannot claim node - code error 28 · Issue #9319 · netdata/netdata · GitHub
@Stavro_Purdie lets change --connect-timeout 5 to --connect-timeout 10
1 Like
@Stavro_Purdie lets check timings
wget https://raw.githubusercontent.com/reorx/httpstat/master/httpstat.py
python httpstat.py "https://app.netdata.cloud"
that is what i get
0 ~ $ python httpstat.py "https://app.netdata.cloud"
Connected to 35.196.244.138:443 from 192.168.50.248:55231
HTTP/2 200
accept-ranges: bytes
cache-control: no-cache
content-length: 2707
content-type: text/html
date: Wed, 17 Mar 2021 10:42:01 GMT
etag: "60511a01-a93"
expires: Thu, 01 Jan 1970 00:00:01 GMT
last-modified: Tue, 16 Mar 2021 20:50:09 GMT
server: nginx/1.17.5
vary: Accept-Encoding
Body stored in: /var/folders/j_/wz4j4ct50v7dxgrkr5pv9drw0000gn/T/tmpbP7eNM
DNS Lookup TCP Connection TLS Handshake Server Processing Content Transfer
[ 5ms | 128ms | 271ms | 129ms | 1ms ]
| | | | |
namelookup:5ms | | | |
connect:133ms | | |
pretransfer:404ms | |
starttransfer:533ms |
total:534ms
1 Like
Both of these sound like really good ideas
I will try them today
I come back with results
