nightscout-librelink-up: nightscout-librelink-up suddenly reports "invalid authentication token".

I’ve been running nightscout-librelink-up sucessfully for about a week now. Tonight at 7:28pm CEST it suddenly stopped working and now reports the following:

[info]: renew token
[error]: "very long string of digits and characters"
[error]: Invalid authentication token. Please check your LibreLink Up credentials Cannot read property 'status' of undefined
[error]: LibreLink Up - No AuthTicket received. Please check your credentials.

The error seems to be caused at line 163 in index.ts: if (response.data.status !== 0)

Any idea what could be causing this? I checked the credentials in the librelink up app - they continue to work there.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 24 (10 by maintainers)

Most upvoted comments

@Blondie-61 i have changed to ip6 only and created a lot of subnetworks. Now every instance runs fine and is not blocked. If you make more connections from one IP (3 Librelink-UP Follower phones should be ok), but if you have more in one wifi, cloudflare blocks the IP from you. What i see.

on 10be runs about 100 librelinkup instances, but now every instances gets a new ip6 address and there are a big range. And after a restart or edit, there get a new ip6 address. I hope there dont block the xxx:xxx:xxx-Net.

@Sidetone602 maybe there blocks first the account and after then the IP. I have automatically check now, that if the status !=0 and it looks, that the login failed, that these librelink instance is automatically disabled.

@timoschlueter I’ve seen similar previously, but i don’t think this is the same here. For example, I am now running a number of docker instances on my Home Lab, for many different regions, and they are all working fine now. It’s a strange one.

@AndyLow91: from my experience its not that Abbott is blocking IP ranges but rather checks if requests are coming from regions where the user is not actually located. I ran into this issue when i hosted my Nightscout and this sidecar on a US server but tried to access data on the LLU endpoint in germany (region “DE”). I was able to resolve the issue by deploying the sidecar to a server hosted in germany.

When I run this locally (in docker) it is working. I have also console.log’d the response.data and can see that the status == 0. But when I’m running the docker container on a remote server, I get the error.

I’ve just tested this on two remote servers, both in different data centres with different hosting companies in two different parts of the world.

I’ll do some more testing…