Is anyone getting captchaed even with a fresh token + new IP address?

[tobeginbegin]

Just encountered this issue this afternoon (9/10). Bot was working fine in the morning. I turned it off after 10am. Tried to turn it on a few hours later and was captchaed as soon as it loaded.

I tried downloading the code again and re-doing everything but still the same result.

Anyone encountering the same issue?

[1-icenine]

I've also been receiving Captcha errors. It started at 5 PM EST yesterday for me.

[SallieAnon28]

It has been at least 6 months since this software is no longer usable and broken. I can see everyone has the same exact issue and it's not getting better. No news, no commits, nothing... I guess the project is dead...

[rommie088]

It has been at least 6 months since this software is no longer usable and broken. I can see everyone has the same exact issue and it's not getting better. No news, no commits, nothing... I guess the project is dead...

The last new version in April fixed the Datadome cookie issue and got most everyone up and running again, but some of us are running into captcha errors again recently.

[Der-Henning]

It has been at least 6 months since this software is no longer usable and broken. I can see everyone has the same exact issue and it's not getting better. No news, no commits, nothing... I guess the project is dead...

This software is not broken.
I build this tool for myself and it is working perfectly for me. And I am happy many people use it too.
I cannot reproduce the problem you and some others have but I wrote everything I know about it in the wiki.

If you have a problem with this tool, leave it or fix it.
This is open source.
If you have any insight on your problem, share it.

Noone will do it for you.

[xusheng-gao]

https://github.com/Der-Henning/tgtg/blob/main/tgtg_scanner/tgtg/tgtg_client.py#L27

I had that 403 and captcha issue. switching from v8 to v9 of the api endpoint in the client got me through.

[tobeginbegin]

https://github.com/Der-Henning/tgtg/blob/main/tgtg_scanner/tgtg/tgtg_client.py#L27

I had that 403 and captcha issue. switching from v8 to v9 of the api endpoint in the client got me through.

Thanks for this. It looks promising. Newbie question: if I'm using the pre-built binary, how would I modify the api endpoint? Am I out of luck?

[xusheng-gao]

Thanks for this. It looks promising. Newbie question: if I'm using the pre-built binary, how would I modify the api endpoint? Am I out of luck?

@tobeginbegin

you can try to build it yourself after making the adjustment: https://github.com/Der-Henning/tgtg?tab=readme-ov-file#build-your-own-binary

[vincentkenny01]

can someone make the change from v8 to v9 on the docker image?

[Der-Henning]

I updated the item endpoint to v9. For me v8 and v9 seem to work fine.
The update is in the edge images. Could you please check if it is working for you?
The new image will be available within the next 15 minutes.

[vincentkenny01]

I updated the item endpoint to v9. For me v8 and v9 seem to work fine. The update is in the edge images. Could you please check if it is working for you? The new image will be available within the next 15 minutes.

thank you for updating the image.

Just tried it and I am getting 'too many captcha errors'. my ip might be blacklisted as it started yesterday. it was working fine for a while until yesterday. maybe I reserved too many bags! will wait for a few days before trying again.

[FaysalBearmani]

Hello
Any answer about this prob ?

I Have Captcha Error

2025-10-06 19:37:54 INFO
2025-10-06 19:37:54 INFO Version 1.23.1
2025-10-06 19:37:54 INFO ©2025, Henning Merklinger
2025-10-06 19:37:54 INFO For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-10-06 19:37:54 INFO
2025-10-06 19:37:54 DEBUG Starting new HTTPS connection (1): api.github.com:443
2025-10-06 19:37:56 DEBUG https://api.github.com:443 "GET /repos/Der-Henning/tgtg/releases/latest HTTP/1.1" 200 1394
2025-10-06 19:37:56 INFO Starting login process ...
2025-10-06 19:37:56 DEBUG Starting new HTTPS connection (1): play.google.com:443
2025-10-06 19:37:57 DEBUG https://play.google.com:443 "GET /store/apps/details?id=com.app.tgtg&hl=en&gl=US HTTP/1.1" 200 None
2025-10-06 19:37:57 DEBUG Using APK version 25.9.21.
2025-10-06 19:37:57 DEBUG Starting new HTTPS connection (1): apptoogoodtogo.com:443
2025-10-06 19:37:58 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:37:58 DEBUG Captcha Error 403!
2025-10-06 19:37:58 DEBUG Starting new HTTPS connection (1): play.google.com:443
2025-10-06 19:37:59 DEBUG https://play.google.com:443 "GET /store/apps/details?id=com.app.tgtg&hl=en&gl=US HTTP/1.1" 200 None
2025-10-06 19:37:59 DEBUG Using APK version 25.9.21.
2025-10-06 19:38:00 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:38:00 DEBUG Captcha Error 403!
2025-10-06 19:38:01 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:38:01 DEBUG Captcha Error 403!
2025-10-06 19:38:02 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:38:04 DEBUG Captcha Error 403!
2025-10-06 19:38:05 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:38:05 DEBUG Captcha Error 403!
2025-10-06 19:38:06 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
2025-10-06 19:38:06 DEBUG Captcha Error 403!
2025-10-06 19:38:07 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 462
2025-10-06 19:38:07 DEBUG Captcha Error 403!
2025-10-06 19:38:08 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 462
2025-10-06 19:38:08 DEBUG Captcha Error 403!
2025-10-06 19:38:09 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 462
2025-10-06 19:38:09 DEBUG Captcha Error 403!
2025-10-06 19:38:10 DEBUG https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 462
2025-10-06 19:38:10 DEBUG Captcha Error 403!
2025-10-06 19:38:10 WARNING Too many captcha Errors! Sleeping for 10 minutes...

[mrv96]

I'm trying this software for the first time, and I'm stuck with too many captcha errors. I tried with two different account but nothing... tgtg-python doesn't work too 😢

[Snowius]

@SallieAnon28

In my opinion @Der-Henning is right because this is not a problem that happens to everybody and he said it himself that he can't reproduce it, so no way for him of trying to fix it by himself. He's also right saying that this is an open source and somebody else can step up and fix it themselves in that case.

That being said, the scanner has not been working for me in the past 6 months due to this issue, so I tried being the person that would fix it and I went into the code. The problem here is pretty simple: as soon as TGTG thinks you are suspicious, you are being faced with a CAPTCHA.

There's only a few solutions to make this work:

1. Avoid the CAPTCHA- which is probably what everybody who does not have this problem is doing. How? You don't decide. TGTG does and if they think your IP, requests or anything else is suspicious they will give you a CAPTCHA to complete and you can't avoid it because your data-dome becomes invalid and they'll only give you a new one once you completed the CAPTCHA.

2. Bypassing the CAPTCHA- This would be possible if the CAPTCHA had poor security, but from my tests (not that deep but I tried) they seem to encrypt some kind of payload attribute (that I could not decrypt) after having verified some of your browser information to make sure you're not a bot.

3. Using an API that can solve CAPTCHA- Probably a good solution here but these are not free. Solving CAPTCHAs programatically is pretty hard and these people have figured a way to solve them, except it costs money. Example: 1.45$ per 1000 CAPTCHAs solved https://2captcha.com/p/datadome-captcha-solver

4. Solving the CAPTCHA manually- Is this possible and/or a good way? In theory, yes but many people including myself run this inside docker in a headless environment. I don't always have a browser to open and solve the CAPTCHA, plus it would not be practical because it could pop back up at any time.

5. Using a python library- For example, Puppeteer or Playwright are able to "spawn browsers" and can make actions. This is not exactly tedious, and could also work in theory since I think they work in headless as well but I don't have much experience with these and I don't know if they can have a "human enough" behavior to pass the first browser verification.

In hindsight, I don't think any of these solutions would be as effective or quick to implement as finding a way to avoid triggering a CAPTCHA in the first place, but this is what I found.

Fun fact, when solving the CAPTCHA they send you to some URL that has both verification about your device, then a verification with a slider puzzle. After the original verification that checks your browser and probably other device information, they send back a data-dome cookie that actually works if you try to plug it inside TGTG. Meaning that I was able to completely bypass the slider puzzle and log into the TGTG bot (after the usual email verification) by using the data-dome cookie returned after the first verification is done.

Anyway, I spent a small 2-3 hours on this but if anyone wants to expand on this matter and find a real solution, let's try :)
And sorry if I used the wrong terminology in my text

[skrzacikus]

I have the same problem with Captcha Error 403 from months, even for new account, new IP, etc.
I switched to https://github.com/hugo-vrijswijk/tgtg
It is working without problems on the same computer, IP and account which has captcha error on @Der-Henning soft