(solved)[Bug]: Failed to connect to https://app.netdata.cloud, return code 7

Question

(solved)[Bug]: Failed to connect to https://app.netdata.cloud, return code 7

Closed this issue 4 months ago · 1 comments

maxzapp commented 5 months ago

Bug description

Adding nodes fails. Installation aborts but agent is locally working.

Expected behavior

Node is added in dashboard

Steps to reproduce

Installation on a Ubuntu 20.4 VM

Screenshots

No response

Error Logs

some tests i made

$dig app.netdata.cloud

; <<>> DiG 9.16.1-Ubuntu <<>> app.netdata.cloud
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47147
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;app.netdata.cloud. IN A

;; ANSWER SECTION:
app.netdata.cloud. 125 IN CNAME main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com.
main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com. 125 IN A 44.196.50.41
main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com. 125 IN A 54.198.178.11
main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com. 125 IN A 44.207.131.212

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fr Feb 09 13:42:50 UTC 2024
;; MSG SIZE rcvd: 165

$nslookup app.netdata.cloud
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
app.netdata.cloud canonical name = main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com.
Name: main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com
Address: 44.196.50.41
Name: main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com
Address: 54.198.178.11
Name: main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com
Address: 44.207.131.212

$ping app.netdata.cloud

PING main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com (44.207.131.212) 56(84) bytes of data.
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=1 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=2 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=3 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=4 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=5 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=6 Destination Host Unreachable
From ubuntu2004.fritz.box (192.168.1.105) icmp_seq=7 Destination Host Unreachable
^C
--- main-ingress-545609a41fcaf5d6.elb.us-east-1.amazonaws.com ping statistics ---
9 packets transmitted, 0 received, +7 errors, 100% packet loss, time 8114ms
pipe 4

$ping 44.196.50.41

PING 44.196.50.41 (44.196.50.41) 56(84) bytes of data.
From 192.168.1.105 icmp_seq=1 Destination Host Unreachable
From 192.168.1.105 icmp_seq=2 Destination Host Unreachable
From 192.168.1.105 icmp_seq=3 Destination Host Unreachable
From 192.168.1.105 icmp_seq=4 Destination Host Unreachable
From 192.168.1.105 icmp_seq=5 Destination Host Unreachable
From 192.168.1.105 icmp_seq=6 Destination Host Unreachable
^C
--- 44.196.50.41 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6150ms
pipe 4

$ping 54.198.178.11

PING 54.198.178.11 (54.198.178.11) 56(84) bytes of data.
From 192.168.1.105 icmp_seq=1 Destination Host Unreachable
From 192.168.1.105 icmp_seq=2 Destination Host Unreachable
From 192.168.1.105 icmp_seq=3 Destination Host Unreachable
^C
--- 54.198.178.11 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4076ms
pipe 4

$ping 44.207.131.212

PING 44.207.131.212 (44.207.131.212) 56(84) bytes of data.
From 192.168.1.105 icmp_seq=1 Destination Host Unreachable
From 192.168.1.105 icmp_seq=2 Destination Host Unreachable
From 192.168.1.105 icmp_seq=3 Destination Host Unreachable
From 192.168.1.105 icmp_seq=4 Destination Host Unreachable
^C
--- 44.207.131.212 ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5066ms
pipe 3

$ping google.com

PING google.com(fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e)) 56 data bytes
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=1 ttl=119 time=6.78 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=2 ttl=119 time=5.18 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=3 ttl=119 time=5.02 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 5.021/5.662/6.783/0.795 ms

$nslookup google.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: google.com
Address: 216.58.206.46
Name: google.com
Address: 2a00:1450:4001:829::200e

ping 216.58.206.46
PING 216.58.206.46 (216.58.206.46) 56(84) bytes of data.
From 192.168.1.105 icmp_seq=1 Destination Host Unreachable
From 192.168.1.105 icmp_seq=2 Destination Host Unreachable
From 192.168.1.105 icmp_seq=3 Destination Host Unreachable
^C
--- 216.58.206.46 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5125ms
pipe 4

Desktop

OS: Hypervisor Unraid OS 6.12.6
Browser [chrome, firefox}

Additional context

Additional 2nd node VM Fedora39 is working fine, locally and in cloud dashboard

Answer 1 · 2024-02-10T09:05:50.000Z

Hi sorry,

it turned out there was a leftover in /etc/hosts from a former hostname change with hostnamectl. After manually change 127.0.1.1 (new hostname)
i was able to connect.