Too many captchas still

[SallieAnon28]

Just updated to 1.25.0 and this is still broken. Not sure if this is supposed to be or if this update was supposed to fix it ?

[light-bit]

Working fine for me. Can you share your config? Like your docker-compose.yml.

[janchrillesen]

FWIW I have the same issue. Started getting captcha errors on 29. december and have been getting them since. I upgraded to the latest version of the scanner when it was released. My compose file contains the following (token and usernames redacted)

services:
  scanner:
    environment:

    - TGTG_USERNAME=user@gmail.com
    - SLEEP_TIME=60
    - TZ=Europe/Berlin
    - LOCALE=da_DK
    - DEBUG=true
    - PORT=7842

    - WEBHOOK=true
    - WEBHOOK_URL=https://api.pushover.net/1/messages.json
    - WEBHOOK_METHOD=POST
    - WEBHOOK_TYPE=application/x-www-form-urlencoded
    - 'WEBHOOK_BODY=token=XXXXXX&user=YYYYYY&message=$${{display_name}} \nAntal: $${{items_available}}\nPris: $${{price}} $${{currency}}\nAfhentning: $${{pickupdate}}'
    - WEBHOOK_CRON=* 6-22 * * *

    volumes:

    ports:
      - 7842:7842

volumes:
      tokens:

Debug logs shows

scanner-1  | 2026-01-26 22:48:00 DEBUG    https://apptoogoodtogo.com:443 "POST /api/token/v1/refresh HTTP/1.1" 403 461
scanner-1  | 2026-01-26 22:48:00 DEBUG    Captcha Error 403!
scanner-1  | 2026-01-26 22:48:05 DEBUG    Starting new HTTPS connection (1): api-sdk.datadome.co:443
scanner-1  | 2026-01-26 22:48:05 DEBUG    https://api-sdk.datadome.co:443 "POST /sdk/ HTTP/1.1" 200 238
scanner-1  | 2026-01-26 22:48:05 DEBUG    Waiting 11 seconds.
scanner-1  | 2026-01-26 22:48:16 DEBUG    https://apptoogoodtogo.com:443 "POST /api/token/v1/refresh HTTP/1.1" 403 461
scanner-1  | 2026-01-26 22:48:16 DEBUG    Captcha Error 403!

[light-bit]

FWIW I have the same issue. Started getting captcha errors on 29. december and have been getting them since. I upgraded to the latest version of the scanner when it was released. My compose file contains the following (token and usernames redacted)

services:
  scanner:
    environment:

    - TGTG_USERNAME=user@gmail.com
    - SLEEP_TIME=60
    - TZ=Europe/Berlin
    - LOCALE=da_DK
    - DEBUG=true
    - PORT=7842

    - WEBHOOK=true
    - WEBHOOK_URL=https://api.pushover.net/1/messages.json
    - WEBHOOK_METHOD=POST
    - WEBHOOK_TYPE=application/x-www-form-urlencoded
    - 'WEBHOOK_BODY=token=XXXXXX&user=YYYYYY&message=$${{display_name}} \nAntal: $${{items_available}}\nPris: $${{price}} $${{currency}}\nAfhentning: $${{pickupdate}}'
    - WEBHOOK_CRON=* 6-22 * * *

    volumes:

    ports:
      - 7842:7842

volumes:
      tokens:

Debug logs shows

scanner-1  | 2026-01-26 22:48:00 DEBUG    https://apptoogoodtogo.com:443 "POST /api/token/v1/refresh HTTP/1.1" 403 461
scanner-1  | 2026-01-26 22:48:00 DEBUG    Captcha Error 403!
scanner-1  | 2026-01-26 22:48:05 DEBUG    Starting new HTTPS connection (1): api-sdk.datadome.co:443
scanner-1  | 2026-01-26 22:48:05 DEBUG    https://api-sdk.datadome.co:443 "POST /sdk/ HTTP/1.1" 200 238
scanner-1  | 2026-01-26 22:48:05 DEBUG    Waiting 11 seconds.
scanner-1  | 2026-01-26 22:48:16 DEBUG    https://apptoogoodtogo.com:443 "POST /api/token/v1/refresh HTTP/1.1" 403 461
scanner-1  | 2026-01-26 22:48:16 DEBUG    Captcha Error 403!

You are not linking your volumes to a local path? volumes: is empty.
Anyway, if you haven't received a PIN via mail - that you then have to enter in the new console (in your case on port 7842). I would say try clearing your token directory first.

[janchrillesen]

Sorry - I removed all lines with # to keep things brief and the token line does include a hashmark. I copy and pasted from https://github.com/Der-Henning/tgtg/blob/main/docker-compose.yml and the config actually reads

services:
[...]
    volumes:
      - tokens:/tokens

    ports:
      - 7842:7842

volumes:
      tokens:

I have created at "tokens" directory in the same directory as my compose file, and the directory is empty. Interesting enough, if I change the path from "tokens" to an absolute pathname (/home/user/tgtg/tokens) the behaviour changes slightly and the captcha happens at another API endpoint

scanner-1  | 2026-01-26 23:26:54 DEBUG    https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
scanner-1  | 2026-01-26 23:26:54 DEBUG    Captcha Error 403!
scanner-1  | 2026-01-26 23:26:59 DEBUG    Starting new HTTPS connection (1): api-sdk.datadome.co:443
scanner-1  | 2026-01-26 23:26:59 DEBUG    https://api-sdk.datadome.co:443 "POST /sdk/ HTTP/1.1" 200 238
scanner-1  | 2026-01-26 23:26:59 DEBUG    Waiting 11 seconds.
scanner-1  | 2026-01-26 23:27:10 DEBUG    https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
scanner-1  | 2026-01-26 23:27:10 DEBUG    Captcha Error 403!
scanner-1  | 2026-01-26 23:27:14 DEBUG    Starting new HTTPS connection (1): api-sdk.datadome.co:443
scanner-1  | 2026-01-26 23:27:15 DEBUG    https://api-sdk.datadome.co:443 "POST /sdk/ HTTP/1.1" 200 238
scanner-1  | 2026-01-26 23:27:15 DEBUG    Waiting 11 seconds.
scanner-1  | 2026-01-26 23:27:26 DEBUG    https://apptoogoodtogo.com:443 "POST /api/auth/v5/authByEmail HTTP/1.1" 403 464
scanner-1  | 2026-01-26 23:27:26 DEBUG    Captcha Error 403!

However still no email and no content of the token directory

[light-bit]

I am using absolute path for more control, I don't like using docker-based volumes (/var/lib/docker/volumes/). But if you do not have any content in that dir, that ain't right.

    volumes:
    - /home/light-bit/containers/tgtg/tokens:/tokens # TGTG credentials

tokens dir

light-bit@vm:~/containers/tgtg/tokens$ ls
accessToken  datadome  refreshToken

Not sure what else you can check. Does the app work on your own phone still, or you also getting CAPTCHA'd there?

[Pavlo-Kk]

If anyone still has 'Captcha Error 403!' issue after updating to the latest version 1.25.0, then you can take a look at this discussion - most probably your IP is banned, and therefore you will need to run it via VPN.

[Arnoudd]

I was also getting 403's after the update. But after killing everything that was polling the TGTG servers for the night everything was working again when I restarted it this morning.

Looks like the ban's do get lifted if you stop polling the servers for a while.

Besides that I think the polling interval is a big factor too. I'm polling once every 5 minutes now to see if this keeps on working.

[janchrillesen]

I think I am affected by the ban as well. I just copied the compose file to my work computer and did a docker compose up, and I am able to login and receive updates now. Of course my computer at work uses a different IP than at home. I will try to disable the scanner at home for 24 hours and try again.

[light-bit]

Of course my computer at work uses a different IP than at home.

Unless your ISP gives you a static Public IP, you could try rebooting your home router and check if you get a new Public IP.
Or like @Pavlo-Kk said, try with a VPN.

[maauso]

Hi all,

I ran into the same “Too many captcha errors” issue and tried a VPN-based workaround using gluetun to route only the TGTG scanner traffic through a VPN.

What I tried:

I set up Docker with qmcgaw/gluetun as a sidecar container using NordVPN (OpenVPN), and configured the TGTG scanner to share its network namespace so all its traffic goes through the VPN tunnel:

gluetun:
  image: qmcgaw/gluetun
  cap_add: [NET_ADMIN]
  devices: ["/dev/net/tun:/dev/net/tun"]
  environment:
    - VPN_SERVICE_PROVIDER=nordvpn
    - VPN_TYPE=openvpn

tgtg:
  image: derhenning/tgtg:latest-alpine
  network_mode: "service:gluetun"
  depends_on: [gluetun]

The result:

Even though the traffic is coming from a different IP, the scanner still ends up hitting the “Too many captcha errors” warning. As already mentioned in this thread, it looks like TGTG is detecting bot-like behavior using more than just the IP address.

One extra note:

Even though the WARNING message still shows up, with this setup I was able, from a clean installation, to successfully configure the login using the ping-based flow, as suggested in version 1.25 of this project. So at least the initial login can be completed following the recommended approach.

About VPNs:

If anyone wants to experiment with a VPN-based setup anyway, ProtonVPN offers a free tier that works well for testing this kind of configuration without any cost.

[aldebaran5470]

Hi, I had same messages. If you are banned, just wait (container down) 24 to 48h. It worked for me.

[KaKi87]

Hi,

I freshly installed it on a new server after not using it for months.

Not only I got the "too many captcha errors" error, but I also got a "RecursionError: maximum recursion depth exceeded" error after a few days of waiting :

scanner-1  | 2026-02-04 08:33:19 INFO     Retrying ...
scanner-1  | 2026-02-04 08:35:23 WARNING  Too many captcha Errors! Sleeping for 10 minutes...
scanner-1  | 2026-02-04 08:45:23 INFO     Retrying ...
scanner-1  | Traceback (most recent call last):
scanner-1  |   File "<frozen runpy>", line 198, in _run_module_as_main
scanner-1  |   File "<frozen runpy>", line 88, in _run_code
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/__main__.py", line 341, in <module>
scanner-1  |     main()
scanner-1  |     ~~~~^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/__main__.py", line 215, in main
scanner-1  |     _run_scanner(scanner)
scanner-1  |     ~~~~~~~~~~~~^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/__main__.py", line 252, in _run_scanner
scanner-1  |     scanner.run()
scanner-1  |     ~~~~~~~~~~~^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/scanner.py", line 172, in run
scanner-1  |     self.tgtg_client.login()
scanner-1  |     ~~~~~~~~~~~~~~~~~~~~~~^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 423, in login
scanner-1  |     response = self._post(
scanner-1  |         AUTH_BY_EMAIL_ENDPOINT,
scanner-1  |     ...<3 lines>...
scanner-1  |         },
scanner-1  |     )
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 366, in _post
scanner-1  |     return self._post(path, **kwargs)
scanner-1  |            ~~~~~~~~~~^^^^^^^^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 366, in _post
scanner-1  |     return self._post(path, **kwargs)
scanner-1  |            ~~~~~~~~~~^^^^^^^^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 366, in _post
scanner-1  |     return self._post(path, **kwargs)
scanner-1  |            ~~~~~~~~~~^^^^^^^^^^^^^^^^
scanner-1  |   [Previous line repeated 965 more times]
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 330, in _post
scanner-1  |     response = self.session.post(
scanner-1  |         self._get_url(path),
scanner-1  |         access_token=self.access_token,
scanner-1  |         **kwargs,
scanner-1  |     )
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 121, in post
scanner-1  |     return super().post(*args, **kwargs)
scanner-1  |            ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/requests/sessions.py", line 637, in post
scanner-1  |     return self.request("POST", url, data=data, json=json, **kwargs)
scanner-1  |            ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 134, in request
scanner-1  |     return super().request(method, url, **kwargs)
scanner-1  |            ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/requests/sessions.py", line 589, in request
scanner-1  |     resp = self.send(prep, **send_kwargs)
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/tgtg_scanner/tgtg/tgtg_client.py", line 112, in send
scanner-1  |     response = super().send(request, *args, **kwargs)
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/requests/sessions.py", line 703, in send
scanner-1  |     r = adapter.send(request, **kwargs)
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/requests/adapters.py", line 644, in send
scanner-1  |     resp = conn.urlopen(
scanner-1  |         method=request.method,
scanner-1  |     ...<9 lines>...
scanner-1  |         chunked=chunked,
scanner-1  |     )
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/urllib3/connectionpool.py", line 787, in urlopen
scanner-1  |     response = self._make_request(
scanner-1  |         conn,
scanner-1  |     ...<10 lines>...
scanner-1  |         **response_kw,
scanner-1  |     )
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/urllib3/connectionpool.py", line 534, in _make_request
scanner-1  |     response = conn.getresponse()
scanner-1  |   File "/opt/venv/lib/python3.13/site-packages/urllib3/connection.py", line 571, in getresponse
scanner-1  |     httplib_response = super().getresponse()
scanner-1  |   File "/usr/local/lib/python3.13/http/client.py", line 1450, in getresponse
scanner-1  |     response.begin()
scanner-1  |     ~~~~~~~~~~~~~~^^
scanner-1  |   File "/usr/local/lib/python3.13/http/client.py", line 355, in begin
scanner-1  |     self.headers = self.msg = parse_headers(self.fp)
scanner-1  |                               ~~~~~~~~~~~~~^^^^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/http/client.py", line 254, in parse_headers
scanner-1  |     return _parse_header_lines(headers, _class)
scanner-1  |   File "/usr/local/lib/python3.13/http/client.py", line 248, in _parse_header_lines
scanner-1  |     return email.parser.Parser(_class=_class).parsestr(hstring)
scanner-1  |            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/email/parser.py", line 64, in parsestr
scanner-1  |     return self.parse(StringIO(text), headersonly=headersonly)
scanner-1  |            ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/email/parser.py", line 53, in parse
scanner-1  |     feedparser.feed(data)
scanner-1  |     ~~~~~~~~~~~~~~~^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/email/feedparser.py", line 176, in feed
scanner-1  |     self._call_parse()
scanner-1  |     ~~~~~~~~~~~~~~~~^^
scanner-1  |   File "/usr/local/lib/python3.13/email/feedparser.py", line 180, in _call_parse
scanner-1  |     self._parse()
scanner-1  |     ~~~~~~~~~~~^^
scanner-1  |   File "/usr/local/lib/python3.13/email/feedparser.py", line 295, in _parsegen
scanner-1  |     if self._cur.get_content_maintype() == 'message':
scanner-1  |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
scanner-1  |   File "/usr/local/lib/python3.13/email/message.py", line 638, in get_content_maintype
scanner-1  |     ctype = self.get_content_type()
scanner-1  |   File "/usr/local/lib/python3.13/email/message.py", line 622, in get_content_type
scanner-1  |     value = self.get('content-type', missing)
scanner-1  |   File "/usr/local/lib/python3.13/email/message.py", line 515, in get
scanner-1  |     return self.policy.header_fetch_parse(k, v)
scanner-1  |            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/email/_policybase.py", line 324, in header_fetch_parse
scanner-1  |     return self._sanitize_header(name, value)
scanner-1  |            ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
scanner-1  |   File "/usr/local/lib/python3.13/email/_policybase.py", line 295, in _sanitize_header
scanner-1  |     if _has_surrogates(value):
scanner-1  |        ~~~~~~~~~~~~~~~^^^^^^^
scanner-1  | RecursionError: maximum recursion depth exceeded

Thanks

[KaKi87]

I guess this project is dying

[Pavlo-Kk]

I guess this project is dying

Why should anything be changed, if it already works well?

[KaKi87]

It does not.