The script stopped working; now I'm getting 403 and 401 and 429 errors

[msgrt]

A few days ago, I manually installed the script on a Raspberry Pi 5 (Bookworm). Everything worked as described. I entered my email, password, and MFA code when I first ran it. After the data from the last 7 days was automatically imported, I fetched the data from the last 5 years. Everything went smoothly.

Two days later, no new data suddenly started appearing in the dashboard. According to the log, this was due to a 403 error.
First, I tried a fresh setup, which was again stopped by a 403 error.
So I deleted the image and ran the setup again. Since then, all attempts have resulted in the same 401 error.

Here’s what else I’ve tried since then:

• Disabled MFA on my Garmin account
• Connected via mobile hotspot
• Connected via VPN
• Waited 2 days between attempts, in case Garmin had temporarily locked the account

I can access my Garmin account from the network where the Raspberry Pi is located without any issues, both from my smartphone and from my PC. So the IP shouldn’t be blocked.

I’m running out of ideas and would appreciate any help.

Here’s the error message:
`2026-03-21 17:19:39,467 - INFO - Trying to login to Garmin Connect using token data from directory '~/.garminconnect'...
2026-03-21 17:19:39,468 - WARNING - Session is expired or login information not present/incorrect. You'll need to log in again...login with your Garmin Connect credentials to generate them.
Enter Garminconnect Login e-mail: xyz@domain.com
Enter Garminconnect password (characters will be visible): password
MFA one-time code (via email or SMS): 123456
2026-03-21 17:20:12,514 - ERROR - 401 Client Error: Unauthorized for url: https://connectapi.garmin.com/oauth-service/oauth/preauthorized?ticket=ST-1231101-JhnG7Kw8dlHdNVvqvk2m-cas&login-url=https://sso.garmin.com/sso/embed&accepts-mfa-tokens=true
Traceback (most recent call last):
File "/app/garmin_grafana/garmin_fetch.py", line 139, in garmin_login
garmin.login(TOKEN_DIR)
~~~~~~~~~~~~^^^^^^^^^^^
File "/app/.venv/lib/python3.13/site-packages/garminconnect/init.py", line 408, in login
self.garth.load(normalized_path)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.13/site-packages/garth/http.py", line 231, in load
with open(os.path.join(dir_path, "oauth1_token.json")) as f:
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/home/appuser/.garminconnect/oauth1_token.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/app/garmin_grafana/garmin_fetch.py", line 153, in garmin_login
garmin.resume_login(result2, mfa_code)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.13/site-packages/garminconnect/init.py", line 542, in resume_login
result1, result2 = self.garth.resume_login(client_state, mfa_code)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.13/site-packages/garth/http.py", line 173, in resume_login
self.oauth1_token, self.oauth2_token = sso.resume_login(
~~~~~~~~~~~~~~~~^
*args, **kwargs
^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 240, in resume_login
return _complete_login(client)
File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 260, in _complete_login
oauth1 = get_oauth1_token(ticket, client)
File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 151, in get_oauth1_token
resp.raise_for_status()
~~~~~~~~~~~~~~~~~~~~~^^
File "/app/.venv/lib/python3.13/site-packages/requests/models.py", line 1024, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://connectapi.garmin.com/oauth-service/oauth/preauthorized?ticket=ST-1231101-JhnG7Kw8dlHdNVvqvk2m-cas&login-url=https://sso.garmin.com/sso/embed&accepts-mfa-tokens=true

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/app/garmin_grafana/garmin_fetch.py", line 1545, in
garmin_obj = garmin_login()
File "/app/garmin_grafana/garmin_fetch.py", line 169, in garmin_login
raise Exception("Session is expired : please login again and restart the script")
Exception: Session is expired : please login again and restart the script`

[arpanghosh8453]

@msgrt Indeed, it's happening all over the garmin ecosystem. This is due to change in Garmin's login endpoint. The garth and python-garminconnect devs are trying hard to get this working.

We use garth by @matin for the authentication as part of the python-garminconnect library by @cyberjunky. follow this thread on their repo cyberjunky/python-garminconnect#332

This is a duplicate of #231 and #232 and in extension to that #20

Please check #20 to stay up to date with this, I will update and release a version as soon as this problem is fixed.

[msgrt]

Ah, okay. I had read all the issue reports up until two days ago, but unfortunately didn't check for new posts when I was writing this today. Please accept my apologies, and thank you very much for your efforts.

[arpanghosh8453]

@msgrt I am not annoyed at all, I expect a good influx of people with this issue, because it makes me feel validates (people are using my project validation haha!)

For me, it's not broken yet, but the account specific changes are being rolled in phases. I am keeping my eyes open and would update ASAP.

[arpanghosh8453]

@msgrt Change the image tag from latest to auth-fix in the compose file for the garmin-fetch-data container and re-deploy with docker compose down && docker compose up -d. We are using a new JWT token based auth flow, and it worked for me. Report back if this works!

[msgrt]

Since I had deleted my credentials during the tests over the past few days, I started with the following after deleting the old image:
docker pull thisisarpanghosh/garmin-fetch-data:auth-fix && docker compose run --rm garmin-fetch-data

New image was pulled:

Status: Downloaded newer image for thisisarpanghosh/garmin-fetch-data:auth-fix
docker.io/thisisarpanghosh/garmin-fetch-data:auth-fix
Pulling image thisisarpanghosh/garmin-fetch-data:latest 

The result was initially a 401; since the second attempt after a break of about 3 hours, it has consistently been a 429.
I saw on cyberjunky/python-garminconnect#332 that this seems to be the case for everyone right now.

[arpanghosh8453]

I am not sure why I see this line in the log you pasted above in addition to the auth-fix tag pulling ``Pulling image thisisarpanghosh/garmin-fetch-data:latest `

But you are right, the current issue is at large. It worked for me for a while and I was able to get the tokens, but I would wait for a better fix, if ever available. Otherwise, the way forward would be the one time import from Garmin export (check readme) script unfortunately.

[msgrt]

I was just as confused, so I changed the tag again. Look what showed up then. Kind of weird, isn't it?

docker pull thisisarpanghosh/garmin-fetch-data:latest && docker compose run --rm garmin-fetch-data
latest: Pulling from thisisarpanghosh/garmin-fetch-data
...
Status: Downloaded newer image for thisisarpanghosh/garmin-fetch-data:latest
docker.io/thisisarpanghosh/garmin-fetch-data:latest
Image thisisarpanghosh/garmin-fetch-data:auth-fix Pulling 
d997cc310c98 Already exists 0B
...
f622e1f93022 Extracting 24.84kB
f622e1f93022 Extracting 24.84kB
f622e1f93022 Pull complete 0B
Image thisisarpanghosh/garmin-fetch-data:auth-fix Pulled 

Thanks for the tip about the Garmin Connect export. I’ll be away on a business trip for a few days, but I’ll definitely check it out when I get back.

Thanks again for all your hard work on this project.
And I hope you get your new drone soon ;)
I’ve had a DJI for years now, and I’m going to give Drone Log a try soon.

[arpanghosh8453]

@msgrt kind of makes sense to me, not 100% sure, but the auth-fix tag can be the latest tag, but ideally it should not.

Have a look at : https://hub.docker.com/r/thisisarpanghosh/garmin-fetch-data/tags

The hashes are clearly different, but idk why they decide to pull the auth-fix tag when latest is specified :(

Anyway, even the auth-fix is not working 100% so I will keep looking at python-garminconnect and garth if they can come up with some solution.

Thank you for your support! It means a lot to me and helps me keep the projects up and running. Check out the new project I launched : https://opendronelog.com (free and OSS platform for drone log analysis) - I am sure you will LOVE it. again. it's challenging some corporate (won't name) existence now - and they are trying hard to keep up haha!

[arpanghosh8453]

@msgrt I have updated the auth-fix tag with the latest version of python-garminconnect 0.3.2 and it seems to be working quite well. Give it a try when you are free. make sure to change the image tag from latest to auth-fix to the compose.yml file and run docker compose pull && docker compose down && docker compose up -d afterward.

[mkowalski]

Hi @arpanghosh8453, I can see you are marking Error 429 (e.g. #242) as duplicate of this one.

In my env it seems to not be fixed. Using thisisarpanghosh/garmin-fetch-data:v0.5.0 image I am getting the following dump

2026-04-28 12:27:47,905 - INFO - Trying to login to Garmin Connect using token data from '~/.garminconnect'...
2026-04-28 12:27:47,906 - WARNING - Session is expired or login information not present/incorrect. You'll need to log in again...login with your Garmin Connect credentials to generate them.
2026-04-28 12:27:48,692 - WARNING - mobile+cffi returned 429: Mobile login returned 429 — IP rate limited by Garmin
2026-04-28 12:27:48,850 - WARNING - mobile+requests returned 429: Mobile login returned 429 — IP rate limited by Garmin
2026-04-28 12:27:55,941 - WARNING - widget+cffi failed: Widget login: unexpected title 'GARMIN Authentication Application'
2026-04-28 12:27:56,239 - INFO - Portal login: waiting 15s to avoid Cloudflare rate limiting...
2026-04-28 12:28:11,690 - INFO - Portal login: waiting 11s to avoid Cloudflare rate limiting...
2026-04-28 12:28:23,287 - INFO - Portal login: waiting 12s to avoid Cloudflare rate limiting...
2026-04-28 12:28:36,146 - INFO - Portal login: waiting 10s to avoid Cloudflare rate limiting...
2026-04-28 12:28:46,693 - INFO - Portal login: waiting 12s to avoid Cloudflare rate limiting...
2026-04-28 12:28:59,300 - WARNING - portal+cffi returned 429: Portal login POST returned 429 — Cloudflare blocking this request.

Let me know if you need any more info, happy to provide whatever is needed.

For completeness, thisisarpanghosh/garmin-fetch-data:auth-fix gives the same exact log dump.

[arpanghosh8453]

@mkowalski Can be a dynamic block rule by Cloudflare! Can't really comment on this!

[mkowalski]

ACK, so what's the status of this issue on your side? Do you consider it fixed in 0.5.0 and any problems are "well, that's life" or are you still actively on this? Either is fine for me, just to know if I should debug more or rather hack my way around