Goodcloud not working for me on a Puli

GoodCloud and Astrorelay
1

Hello. I have a Puli and it was working fine with Goodcloud but now its not, I can register the device but any action give a device offline warming. I am on the same Europe region.

Any help welcome,
Dean

2

Sat Apr 13 13:57:12 2024 daemon.debug eco: (gl-cloud:232) fetch server from: https://gslb-eu.goodcloud.xyz/gslb/getbucket?deviceType=1&mac=9483c446d867&sn=84e21047c74195c0&ddns=gd6d867&timestamp=1713009432&sign=4500b838993e0a07406ddc5b052a75c9
Sat Apr 13 13:57:12 2024 daemon.err eco: (gl-cloud:236) fetch server fail: resolve “gslb-eu.goodcloud.xyz” fail: server failure
Sat Apr 13 13:57:12 2024 daemon.err eco: (gl-cloud:503) reconnect mqtt in 5s…
Sat Apr 13 13:57:17 2024 daemon.debug eco: (gl-cloud:232) fetch server from: https://gslb-eu.goodcloud.xyz/gslb/getbucket?deviceType=1&mac=9483c446d867&sn=84e21047c74195c0&ddns=gd6d867&timestamp=1713009437&sign=aa7d0058849b8edfa97200fa3537db48
Sat Apr 13 13:57:17 2024 daemon.err eco: (gl-cloud:236) fetch server fail: resolve “gslb-eu.goodcloud.xyz” fail: server failure
Sat Apr 13 13:57:17 2024 daemon.err eco: (gl-cloud:503) reconnect mqtt in 5s…

3

Do you use special DNS servers or AdGuard Home?
Make sure to exclude *.goodcloud.xyz from them, so they are able to be resolved.

4

no, its on French SFR Mobile, internet is working fine. The DNS servers are assigned by the mobile provider I think as ive not touched them 172.20.2.39 , 172.20.2.10

5

also did this

root@GL-XE300:~# curl -v https://gslb-eu.goodcloud.xyz/getCaCert/ca.crt

  • Could not resolve host: gslb-eu.goodcloud.xyz

curl: (6) Could not resolve host: gslb-eu.goodcloud.xyz

root@GL-XE300:~#

6

It’s a DNS issue. But I don’t know why it happens.
Try to select another DNS server, maybe they block it somehow.

7

Thanks is there a specific or best DNS to use?
D

8

Any DNS is OK.
Google: 8.8.8.8
Quad9: 9.9.9.9
Cloudflare: 1.1.1.1

And all the others.

9

Thanks… annoyingly, no matter what I change it to the mobile provider has Locked it to its own.

10

Probably it is a firmware issue. Downgrade the firmware to 4.3.7 and see if this fix it

11

no, its not a firmware issue as it was working on the same firmware on a now its now. Thanks