problem: "TgtgCaptchaError"

[danielblogo89]

Hi Henning,

since today i've got the following error code:
(<class 'models.errors.TgtgCaptchaError'>, TgtgCaptchaError(403, b'<title>apptoogoodtogo.com</title><style>#cmsg{animation: A 1.5s;}@Keyframes A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style>

Please enable JS and disable any ad blocker

Do you know how to fix it?

all the best

[danielblogo89]

now i have tested it with the newest scanner version and got this error:

2023-05-25 17:06:28 WARNING Too many captcha Errors! Sleeping for 10 minutes...

[pershoot]

@Der-Henning Hi. I noticed the same thing after not receiving notifs., for today. I went for a new setup to observe and after login, it tries to get through captcha and also reports: 'Too many captcha Errors! Sleeping for 10 minutes...'. I waited for two successions before rolling back my tokens that were in place. Thank you.

[danielblogo89]

Hope TGTG did not find a solution to ban the scanner :(

[djan271991]

"I have the same problem today

[ArcCdr]

FYI, same issue for me as well.
If it helps:

2023-05-25 18:51:07 INFO     Scanner reenabled by cron schedule.
2023-05-25 18:51:07 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:07 DEBUG    Captcha Error 403!
2023-05-25 18:51:07 DEBUG    Starting new HTTPS connection (1): play.google.com:443
2023-05-25 18:51:07 DEBUG    https://play.google.com:443 "GET /store/apps/details?id=com.app.tgtg&hl=en&gl=US HTTP/1.1" 200 None
2023-05-25 18:51:07 DEBUG    Using APK version 23.4.12.
2023-05-25 18:51:08 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:08 DEBUG    Captcha Error 403!
2023-05-25 18:51:09 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:09 DEBUG    Captcha Error 403!
2023-05-25 18:51:10 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:10 DEBUG    Captcha Error 403!
2023-05-25 18:51:11 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:11 DEBUG    Captcha Error 403!
2023-05-25 18:51:12 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:12 DEBUG    Captcha Error 403!
2023-05-25 18:51:13 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 405
2023-05-25 18:51:13 DEBUG    Captcha Error 403!
2023-05-25 18:51:14 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:14 DEBUG    Captcha Error 403!
2023-05-25 18:51:15 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 405
2023-05-25 18:51:15 DEBUG    Captcha Error 403!
2023-05-25 18:51:16 DEBUG    https://apptoogoodtogo.com:443 "POST /api/item/v7/ HTTP/1.1" 403 406
2023-05-25 18:51:16 DEBUG    Captcha Error 403!
2023-05-25 18:51:16 WARNING  Too many captcha Errors! Sleeping for 10 minutes...

[nikoonline3]

I got a capcha request with an image on my smartphone when I launched the app.

"A bot has been found on your network..."

[antonioli86]

Same here. :(
Possible solution: ahivert/tgtg-python#241 (comment) ?

[danielblogo89]

Same here. :( Possible solution: ahivert/tgtg-python#241 (comment) ?

too technical for me :((((

[Der-Henning]

Hi.
I can confirm the observed behavior. I don't have a solution at the moment, but I am looking into it.

@antonioli86 The datadome cookie is already implemented.

I will give you an update if I find a solution.
Feel free to post any possible solutions or workarounds.

[danielblogo89]

I have testet is even with my phones wifi but it did not work either...

[Der-Henning]

Update:
TGTG changed their API. A small update 12dbc57 should do the trick. I will create a new release as soon as possible.

[pershoot]

@Der-Henning Built from dev; received initial test and another notif. right after that. I'll monitor. Thank you.

[Der-Henning]

I created a new release v1.16.3 containing the new API endpoint as a hotfix as it seems to work for now. Please note if you have any problems or notice any strange behavior. Thank you.

[antonioli86]

I created a new release v1.16.3 containing the new API endpoint as a hotfix as it seems to work for now. Please note if you have any problems or notice any strange behavior. Thank you.

Will push new image in Docker Hub?

edit: I see now - By derhenning • Updated 2 minutes ago

[Der-Henning]

@antonioli86 Yes the CI/CD takes some minutes to create the release binaries and docker images. But it just completed.

[antonioli86]

@antonioli86 Yes the CI/CD takes some minutes to create the release binaries and docker images. But it just completed.

Thanks. Just did pull and seems all fine now. Thanks!

[danielblogo89]

I created a new release v1.16.3 containing the new API endpoint as a hotfix as it seems to work for now. Please note if you have any problems or notice any strange behavior. Thank you.

Thank you, but on my end it seems to not work

[Der-Henning]

@danielblogo89
Sometimes it helps to relogin to the TGTG API. To do so delete the saved tokens, userid and datadome cookie. Or you have to wait for some time.

[nikoonline3]

Work for me !

[nikoonline3]

for docker I need to use a specific tag "image: derhenning/tgtg:v1.16.3". With latest I have version 1.16.2.

[Der-Henning]

Hi @nikoonline3.
You have to make sure that you repulled the latest image. Otherwise docker uses the current local image with the specified tag.
Using docker compose you can update the local image with docker-compose pull or use docker pull derhenning/tgtg:latest.

[Der-Henning]

@danielblogo89 Is it working for you now?

[karimhajji12]

I have the same problem that @danielblogo89. Maybe my IP is blocked, because there's this error (too many captchas) only with my personal Wifi, when is switch my internet connection there's no error. As you can see when I connect to my home wi-fi at 17:56 it doesn't work anymore.

[SergiBaucells]

The same thing happens to me as to @karimhajji12 . The same computer on the network that has always been configured and working gives the captcha error and if I change the network it does work for me.

[SergiBaucells]

Extra information: without touching anything, it has been working for 1 day, but now I get the 403 problem again.

[Zilverdael80]

I have the same issue, running latest version 1.16.3