Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Index Scale no longer connects

daryljmullen
over 4 years ago

Has anyone fixed this yet?

I‘m unable to connect to WiFi. 
Tried all the suggested fixes splitting the WiFi signal, using the stick, using hotspot, resetting etc. 

Something clearly happened a couple of weeks ago. 

Come on Garmin the forum is littered with dozens of similar posts. 

  • 0 over 4 years ago in reply to sevk

    Well yes... but it seems after that it tries to connect to gold.garmin.com and then nothing happens...

    I don't know what does gold.garmin.com ...

    I did a full reset, use provider dns > no change...

    Now I'am using my internal DNS with google as forwarder (tried with a lot of DNS as forwarder) > no change
    I'm using my internal DNS to alias the clock.garmin.com name :)

  • 0 over 4 years ago in reply to pakal

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    19 Apr 13:37:31 ntpdate[29484]: no server suitable for synchronization found

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    19 Apr 13:37:36 ntpdate[29494]: no server suitable for synchronization found

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    19 Apr 13:37:39 ntpdate[29503]: no server suitable for synchronization found

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    server 204.77.162.174, stratum 3, offset -0.008160, delay 0.18127

    19 Apr 13:37:40 ntpdate[29512]: adjust time server 204.77.162.174 offset -0.008160 sec

  • 0 over 4 years ago in reply to pakal

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    server 204.77.162.174, stratum 3, offset -0.007071, delay 0.18312

    19 Apr 13:37:59 ntpdate[29557]: adjust time server 204.77.162.174 offset -0.007071 sec

    sevk@pi4:~ $ sudo ntpdate -q 204.77.162.174

    19 Apr 13:38:02 ntpdate[29566]: no server suitable for synchronization found

    sevk@pi4:~ $ sudo ntpdate -q clock.garmin.com

    server 192.89.123.28, stratum 3, offset 0.000092, delay 0.03709

    19 Apr 13:40:10 ntpdate[29648]: adjust time server 192.89.123.28 offset 0.000092 sec

    sevk@pi4:~ $ sudo ntpdate -q clock.garmin.com

    server 192.89.123.28, stratum 3, offset -0.000208, delay 0.03644

    19 Apr 13:40:13 ntpdate[29657]: adjust time server 192.89.123.28 offset -0.000208 sec

    sevk@pi4:~ $ sudo ntpdate -q clock.garmin.com

    server 192.89.123.28, stratum 3, offset 0.003259, delay 0.04219

    19 Apr 13:40:15 ntpdate[29666]: adjust time server 192.89.123.28 offset 0.003259 sec

  • 0 over 4 years ago in reply to sevk

    So, at the end, it doesn't really seems related to 1.1.1.1 ...

    There is some issue on Garmin infrastructure...

  • 0 over 4 years ago in reply to sevk

    Yep I did that too, aliasing clock.garmin.com but it doesn't solve the problem.
    I see a query to gold.garmin.com but after that nothing...

    ─root@pi60-tools ~
    ╰─➤ ntpdate -q clock.garmin.com
    server 172.16.8.32, stratum 3, offset 0.001415, delay 0.02602
    19 Apr 12:43:22 ntpdate[15045]: adjust time server 172.16.8.32 offset 0.001415 sec

  • 0 over 4 years ago in reply to pakal

    There is 3th domain also, api.gcs.garmin.com. 

  • 0 over 4 years ago in reply to pakal

    After I changed Pihole settings to Quad9, zero problems after that. 

  • 0 over 4 years ago in reply to sevk

    As I did a full reset it doesn't go further than gold.garmin.com ...
    Anyway today my 5 years old Index scale is a brick ...

  • 0 over 4 years ago in reply to sevk

    DNS change nothing for me...