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

Unable to view full pages

Former Member over 11 years ago

I'm unable to vie the full page for Steps sleep

When I try to view full page it does nothing, been doing this for 2 days now. Even when trying from the menu on the left.

Anyone else?

Top Replies

e7andy over 3 years ago in reply to pshare +1

My guess is that it got something to do with the DNS and the name resolution. Maybe Garmin moved some servers. Then it should fix itself after a while when the records are updated. It can also be something…
reflecx over 3 years ago in reply to pshare +1

I'm facing the same issue with Web on Firefox, so you're not the only one
reflecx over 3 years ago in reply to BunBun! +1

This is the URL that gets a 401 Unauthorized. The Authorization header is being sent, so it is a problem on the server side

connect.garmin.com/.../usageIndicators

All Replies

0 VA over 3 years ago

I had the same problem. The solution for me was to change (revert back) my primary IPv4 DNS server to 8.8.8.8 and IPv6 DNS server to 2001:4860:4860::8888. After that I did a ipconfig /flushdns in PowerShell.

0 pshare over 3 years ago in reply to VA

I'm already on 8.8.8.8 so I flushed my dns.

Still doesn't work,

Maybe I'll try 1.1.1.1

0 VA over 3 years ago in reply to pshare

Try "changing", and i do stress on the changing part, to 8.8.4.4 and to 2001:4860:4860::8844. I do not know if you are on a IPv4 or IPv6, so changing them both might do the trick. and flush the dns afterwards

0 VA over 3 years ago in reply to VA

2606:4700:4700::1111 if you are using 1.1.1.1

0 pshare over 3 years ago in reply to VA

No change with any of the DNS options.

0 reflecx over 3 years ago in reply to pshare

Garmin probably has a farm of servers, I suspect some of these servers are working, and some are having the issue. I'm still facing the issue intermittently.

0 reflecx over 3 years ago in reply to reflecx

Can more or less confirm my theory. When I encounter this, multiple reloads of the page will not solve the issue. I just restart the browser to get another session, then the sleep page loads. It might be that different servers are on different versions of their API, incompatibility issue.

0 pshare over 3 years ago in reply to reflecx

Well, after a couple of weeks where I couldn't get it to work, restarting the browser did the trick. In the words of Staples: "Well, THAT was EASY!"