Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Payment Required?
See original GitHub issueGreetings.
Is anyone else encountering the Payment Required message/error after authentication?
[ERROR] Failed to reach url https://connect.garmin.com/modern/proxy/activitylist-service/activities/search/activities?start=0&limit=1, error: HTTP Error 402: Payment Required
Everything was fine as of last night.
My best, Gowtham
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
402 Payment Required - HTTP - MDN Web Docs
The HTTP 402 Payment Required is a nonstandard response status code that is reserved for future use. This status code was created to...
Read more >What Is the HTTP 402 Status Code? - Kinsta
The HTTP 402 or “Payment Required” code isn't a standard response, and most browsers don't use it. Therefore, if you see a 402...
Read more >402 Payment Required - HTTP Status Code Glossary - WebFX
HTTP Status Code 402: Reserved for future use.
Read more >Required Payment Definition: 639 Samples - Law Insider
Required Payment means all con- sideration that the franchisee must pay to the franchisor or an affiliate, ei- ther by contract or by...
Read more >Getting status code '402 Payment Required'
The 402 Payment Required status code means that the private feed is locked because the feed owner's subscription has expired.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Should be fixed by the PR #55, I released v3.0.3
there’s a good hint in https://github.com/tcgoetz/GarminDB/issues/109#issuecomment-785047086 and adding that mentioned header in various requests indeed seems to fix this issue.