search

timoschlueter / nightscout-librelink-up

Script written in TypeScript that uploads CGM readings from LibreLink Up to Nightscout.
MIT License
200 stars 252 forks source link

Invalid authentication token. Please check your LibreLink Up credentials #160

Open n8scout opened 2 months ago

n8scout commented 2 months ago

Hi there!

I am in linkup hell. Maybe you guys can help.

I tried various docker hosts from our cloud, germany and helsinki, since my first thought was some sort of ip ban. But it seems like to only machine i can get to work is a docker host behind my home dial up connection. All the others come up with the error mentioned above.

nightscout-librelink-up@2.7.0 start-heroku node dist/index.js [info]: Starting cron schedule: /5 * [info]: renew token [error]: [error]: Invalid authentication token. Please check your LibreLink Up credentials Cannot read properties of undefined (reading 'status') [error]: LibreLink Up - No AuthTicket received. Please check your credentials.

It is not the credentials, they work. I even tried setting up a new linkup account, nope. Right now my only working setup is a docker in my cloud server for nightscout and mongo and the link up module on my home server. Can anyone please help? Would be much appreciated. Thanks in advance!

n8scout commented 2 months ago

Just an additional info...

Right now, I got the link up module up and running on my helsinki server. Same configuration as the others. Is it really some sort of IP blocking or banning?

ThomasQuant commented 1 month ago

Any update on this error? Starting to get sick of having to restart every day, sometimes several times, and waiting for it to suddenly work again.

Have tried all the suggestions in other similar threads. None work.

n8scout commented 1 month ago

Hi Thomas!

The only thing I can give is, that sometimes the linkup portal starts to block certain IP adress ranges. My servers run in Hetzner locations. So I guess if one customer of hetzner starts doing stupid stuff with their portal ,they block the whole ip range. My only solution so far is, to run multiple docker instances in multiple locations and then switch between them once they are being blocked. Of course that shit happens mostly a night and triggers my alarm on my cgm monitoring... I even tried calling their hotline, but they can not help, didn't think so, and they say even their second level support could not help, because they simply offer a service, what I can or can not do with it is my personal problem as long as the service itself is running, which it is as you can see from your app... I wonder how pro hosters address this issue? Sorry for not having the super solution on this...