TGTG API Error: (404, b'') #579

EtotheM · 2025-02-26T07:35:29Z

Hey guys,

since yesterday iam getting the Error: " TGTG API Error: (404, b'')" in my docker. Does anyone else have the same problem?
I tried the Windows version but the same problem appears there too.

nibbler75 · 2025-02-26T10:39:20Z

2025-02-25 12:47:58 ERROR (404, b'')

I have the same error since yesterday at 12.47 PM

I am stuck eversince. i tried to reinstall the app but it was a no go.
also when i reinstalled a new error appeared, Windows defender claimed that the ZIP package of the windows version i downloaded from there had a trojan : Trojan:Script/Wacatac.B!ml

webfile: Z:\temp\scanner-v1.22.0-win.zip|https://objects.githubusercontent.com/github-production-release-asset-2e65be/318623421/54c2c004-3b58-41ad-adbd-e4596ced490b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=releaseassetproduction%2F20250225%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250225T160131Z&X-Amz-Expires=300&X-Amz-Signature=23f0c3db2ef2d62960a5e134ec0f9d2e00451d82716a9522fb3f3d9537499974&X-Amz-SignedHeaders=host&response-content-disposition=attachment%3B%20filename%3Dscanner-v1.22.0-

i whitelisted it, hopefuly nothing bad will happen to my PC :)

vyskoczilova · 2025-02-26T15:31:50Z

Me too (on Linux server), any ideas?

p3g4asus · 2025-02-26T17:33:44Z

Same problem here. My platform is Linux server.

p3g4asus · 2025-02-26T19:43:51Z

I succeeded to start the scanner again, forcing it to re-sign in. You can do this by deleting from config file the lines AccessToken, RefreshToken and Datadome. It will send an email with a confirmation link to login. The problem is that every time you restart the scanner you have to repeat the procedure. Otherwise you will get 404 error. I will try to understand what is the API call that fails ASAP.

Der-Henning · 2025-02-26T19:53:40Z

Hi @p3g4asus. I can confirm this is working. They seem to have changed something in the token management and the old tokens are not valid anymore. I will add an error message that will suggest to this solution. This will only be a temporary solution until we know how the new refresh token works.

steff94 · 2025-02-26T21:07:57Z

Same error since tonight:

2025-02-26 22:05:22 INFO     Loaded config from environment variables
2025-02-26 22:05:22 INFO       ____  ___  ____  ___    ____   ___   __   __ _  __ _  ____  ____  
2025-02-26 22:05:22 INFO      (_  _)/ __)(_  _)/ __)  / ___) / __) / _\ (  ( \(  ( \(  __)(  _ \ 
2025-02-26 22:05:22 INFO        )( ( (_ \  )( ( (_ \  \___ \( (__ /    \/    //    / ) _)  )   / 
2025-02-26 22:05:22 INFO       (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
2025-02-26 22:05:22 INFO     
2025-02-26 22:05:22 INFO     Version 1.22.1
2025-02-26 22:05:22 INFO     ©2025, Henning Merklinger
2025-02-26 22:05:22 INFO     For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-02-26 22:05:22 INFO     
2025-02-26 22:05:23 ERROR    TGTG API Error: (404, b'')
2025-02-26 22:05:57 INFO     Loaded config from environment variables
2025-02-26 22:05:57 INFO       ____  ___  ____  ___    ____   ___   __   __ _  __ _  ____  ____  
2025-02-26 22:05:57 INFO      (_  _)/ __)(_  _)/ __)  / ___) / __) / _\ (  ( \(  ( \(  __)(  _ \ 
2025-02-26 22:05:57 INFO        )( ( (_ \  )( ( (_ \  \___ \( (__ /    \/    //    / ) _)  )   / 
2025-02-26 22:05:57 INFO       (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
2025-02-26 22:05:57 INFO     
2025-02-26 22:05:57 INFO     Version 1.22.1
2025-02-26 22:05:57 INFO     ©2025, Henning Merklinger
2025-02-26 22:05:57 INFO     For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-02-26 22:05:57 INFO     
2025-02-26 22:05:57 ERROR    TGTG API Error: (404, b'')

Workaround from @p3g4asus works fine:

2025-02-26 22:10:59 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 22:11:04 INFO     Logged in!
2025-02-26 22:11:04 WARNING  Username and Password or Access Token missing for Ntfy authentication, defaulting to no auth
2025-02-26 22:11:04 INFO     Activated notifiers:
2025-02-26 22:11:04 INFO     - Ntfy: https://ntfy.sh/XXXX
2025-02-26 22:11:04 INFO     Sending test Notifications ...
2025-02-26 22:11:04 INFO     Scanner started ...

But as soon as I restart the container, the same error appears:

2025-02-26 22:12:05 INFO     Loaded config from environment variables
2025-02-26 22:12:05 INFO       ____  ___  ____  ___    ____   ___   __   __ _  __ _  ____  ____  
2025-02-26 22:12:05 INFO      (_  _)/ __)(_  _)/ __)  / ___) / __) / _\ (  ( \(  ( \(  __)(  _ \ 
2025-02-26 22:12:05 INFO        )( ( (_ \  )( ( (_ \  \___ \( (__ /    \/    //    / ) _)  )   / 
2025-02-26 22:12:05 INFO       (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
2025-02-26 22:12:05 INFO     
2025-02-26 22:12:05 INFO     Version 1.22.1
2025-02-26 22:12:05 INFO     ©2025, Henning Merklinger
2025-02-26 22:12:05 INFO     For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-02-26 22:12:05 INFO     
2025-02-26 22:12:07 ERROR    TGTG API Error: (404, b'')

ihor-chaban · 2025-02-27T01:27:32Z

It doesn't work for me even after deleting the tokens and with a fresh login.

2025-02-26 20:15:45 INFO     Loaded config from environment variables
2025-02-26 20:15:45 WARNING  No token files in token path.
2025-02-26 20:15:45 INFO       ____  ___  ____  ___    ____   ___   __   __ _  __ _  ____  ____  
2025-02-26 20:15:45 INFO      (_  _)/ __)(_  _)/ __)  / ___) / __) / _\ (  ( \(  ( \(  __)(  _ \ 
2025-02-26 20:15:45 INFO        )( ( (_ \  )( ( (_ \  \___ \( (__ /    \/    //    / ) _)  )   / 
2025-02-26 20:15:45 INFO       (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
2025-02-26 20:15:45 INFO     
2025-02-26 20:15:45 INFO     Version 1.22.1
2025-02-26 20:15:45 INFO     ©2025, Henning Merklinger
2025-02-26 20:15:45 INFO     For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-02-26 20:15:45 INFO     
2025-02-26 20:15:45 INFO     Starting login process ...
2025-02-26 20:15:46 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 20:15:51 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 20:15:57 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 20:16:02 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 20:16:07 WARNING  Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-02-26 20:16:13 INFO     Logged in!
2025-02-26 20:16:13 INFO     Activated notifiers:
2025-02-26 20:16:13 INFO     - Telegram: ['XXXXXXXXX']
2025-02-26 20:16:13 INFO     Scanner started ...
2025-02-26 20:16:22 WARNING  Too many captcha Errors! Sleeping for 10 minutes...
2025-02-26 20:26:22 INFO     Retrying ...
2025-02-26 20:26:33 WARNING  Too many captcha Errors! Sleeping for 10 minutes...

p3g4asus · 2025-02-27T08:16:00Z

Unfortunately scanner stops working after some time and in the log I find:
[2025-02-27 08:09:49][tgtg][scanner.py:run:197][INFO] Scanner reenabled by cron schedule.
[2025-02-27 08:09:49][tgtg][scanner.py:_get_favorites:132][ERROR] (404, b'')

p3g4asus · 2025-02-27T15:46:52Z

It seems that, after starting the scanner by re-signing in, the scanner works just fine for 4 hours. After that, it starts giving 404 error in _get_favorites. So, in theory, the scanner should be restarted with new sign in every less than 4 hours.

Der-Henning · 2025-02-27T19:17:07Z

As a temporary improvement you can set the TGTG_ACCESS_TOKEN_LIFETIME config parameter. The default is 14400 seconds for 4 hours. After this time the scanner tries to refresh the token, which is failing at the moment.
I don't know the actual lifetime of the access token but it should be longer than 4 hours.

p3g4asus · 2025-02-27T19:54:48Z

As a temporary improvement you can set the TGTG_ACCESS_TOKEN_LIFETIME config parameter. The default is 14400 seconds for 4 hours. After this time the scanner tries to refresh the token, which is failing at the moment.
I don't know the actual lifetime of the access token but it should be longer than 4 hours.

Thank you for the suggestion: I set

AccessTokenLifetime = 90000

under TGTG session. I will report if it works all the time or stops before the end.

ShotaArveladze24 · 2025-02-27T20:04:09Z

Hi, for the Windows app I resolved like this:

Create a batch
del "D:\path\scanner-v1.22.1-win\config.ini"
copy /y "D:\path\scanner-v1.22.1-win\config_template.ini" "D:\PYTHON\scanner-v1.22.1-win\config.ini"
D:\path\scanner-v1.22.1-win\scanner.exe

Basically, I created a version of the config file without AccessToken, RefreshToken and Datadome; then I copy&rename the template file and relaunch the application. It requires to validate a mail (not a problem) but , then, by enabling the Debug, I see something like this:

[2025-02-27 20:55:54][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:54][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:55][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:55][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:56][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:56][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:56][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 406
[2025-02-27 20:55:56][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:57][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:57][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:57][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:57][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:58][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:58][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:58][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:58][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:59][urllib3.connectionpool][connectionpool.py:_make_request:544][DEBUG] https://apptoogoodtogo.com:443 "POST /api/item/v8/ HTTP/1.1" 403 411
[2025-02-27 20:55:59][tgtg][tgtg_client.py:_post:202][DEBUG] Captcha Error 403!
[2025-02-27 20:55:59][tgtg][tgtg_client.py:_post:212][WARNING] Too many captcha Errors! Sleeping for 10 minutes...

But the login itself worked well, actually this error appeared after connecting to my Telegram bot.

niklasdoerfler · 2025-02-27T20:28:48Z

I've got exactly the same behavior. Login succeeds (with a fresh config.ini without the tokens and after mail confirmation), but the I also get the 403 captcha errors after telegram tries to send the test notification. The 403 is probably issues by the request to '/api/item/v8/'.

p3g4asus · 2025-02-27T20:40:36Z

I've got exactly the same behavior. Login succeeds (with a fresh config.ini without the tokens and after mail confirmation), but the I also get the 403 captcha errors after telegram tries to send the test notification. The 403 is probably issues by the request to '/api/item/v8/'.

I use telegram as notifier too but I don't get any 403 captcha error. I think that some API endpoint URL path was changed in a recent commit. Maybe the URL change was not spread all over the world?

p3g4asus · 2025-02-27T20:48:24Z

I've got exactly the same behavior. Login succeeds (with a fresh config.ini without the tokens and after mail confirmation), but the I also get the 403 captcha errors after telegram tries to send the test notification. The 403 is probably issues by the request to '/api/item/v8/'.

Or it could be some anti spam prevention. Did you try to open too good to go app to see if you get any captcha there?

niklasdoerfler · 2025-02-27T21:07:08Z

Or it could be some anti spam prevention. Did you try to open too good to go app to see if you get any captcha there?

Yes, I tried to open the app and it works without any issues. Captchas are also not shown there. (App and tgtg-scanner share the same network, so the outgoing IP is also the same). I also tried running the scanner on a different server outside my home network, which leads to the same behavior.

antonioli86 · 2025-02-27T23:23:16Z

New refresh url is at: /api/token/v1/refresh
ahivert/tgtg-python#335 (comment)

ihor-chaban · 2025-02-28T00:19:38Z

I'm still getting 403 error at item/v8/
Maybe they haven't rolled out this change everywhere yet, but this endpoint has also changed (and maybe some others too).

I tried changing v8 -> v9 and v10 but it didn't work.

My app version is 25.2.11 now.

upd. It looks like the latest APK version is indeed available only in some countries now.
I wanted to intercept app requests to check the endpoints version and address, but I could get 25.2.11 APK from anywhere. And I couldn't download it from Google Play via third-party tools as they all showed that 25.2.0 version is the latest. I think in a couple of days it should become available globally.

p3g4asus · 2025-02-28T06:14:14Z

New refresh url is at: /api/token/v1/refresh
ahivert/tgtg-python#335 (comment)

This does work but you have to modify REFRESH_ENDPOINT in tgtg/tgtg_client.py setting it to "token/v1/refresh".
Thanks for sharing.

Der-Henning · 2025-02-28T08:26:10Z

Release 1.22.2 is build right now. It implements the new refresh token endpoint.

steff94 · 2025-02-28T09:06:58Z

@Der-Henning thanks! 1.22.2 works like a charm!

Moley123 · 2025-02-28T11:55:46Z

I have updated the scanner to 1.22.2 but I'm still getting the captcha error.

Anyone else?

vyskoczilova · 2025-02-28T12:32:25Z

@Moley123 Me to, I've even deleted the credentials and signed again, but the issue persists. :(

ihor-chaban · 2025-02-28T16:11:20Z

I just intercepted requests from 25.2.11 app.
They don't use item/v8/ endpoint anymore, they use discover/v1/bucket instead.
Attaching full request/response below.

It looks like they will also be migrating other endpoints to something/v1/something
They already changed token refresh and items endpoints to this new schema.

tgtg-25.2.11-request.txt

ihor-chaban · 2025-02-28T16:37:57Z

upd. I still see item/v8 endpoint when opening a particular item, but it looks like favorites list was migrated to discover/v1/bucket

Here I tried refreshing favorites, then opened an item and tried reserving it.

ShotaArveladze24 · 2025-03-01T18:38:35Z

Hello, am I the only one that is still getting the same error? Login ok, launching the Telegram bot also ok, then KO when start scanning my favourites

p3g4asus · 2025-03-01T19:54:27Z

Hello, am I the only one that is still getting the same error? Login ok, launching the Telegram bot also ok, then KO when start scanning my favourites

One question: how many favourites do you have? How many surprise bag types do you have on average from your favourites?
I am trying to understand why I am not getting this issue. I have examined the app behaviour and it actually uses different rest calls from the ones used by this scanner. But the scanner continues working perfectly in my setup.

vyskoczilova · 2025-03-02T17:38:17Z

I have just 2 favourites, and I'm getting troubles with recaptcha:

[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:289][INFO]   (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:290][INFO] 
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:291][INFO] Version 1.22.2
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:293][INFO] ©2025, Henning Merklinger
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:294][INFO] For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:295][INFO] 
[2025-03-02 18:29:48][tgtg][notifiers.py:__init__:28][INFO] Activated notifiers:
[2025-03-02 18:29:48][tgtg][notifiers.py:__init__:32][INFO] - Telegram: ['471886404']
[2025-03-02 18:29:48][tgtg][scanner.py:run:189][INFO] Sending test Notifications ...
[2025-03-02 18:29:57][tgtg][tgtg_client.py:_post:212][WARNING] Too many captcha Errors! Sleeping for 10 minutes...

and the same I get when I try to log in again:

[2025-03-02 18:37:05][tgtg][tgtg_client.py:start_polling:299][WARNING] Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
[2025-03-02 18:37:11][tgtg][tgtg_client.py:start_polling:305][INFO] Logged in!
[2025-03-02 18:37:11][tgtg][notifiers.py:__init__:28][INFO] Activated notifiers:
[2025-03-02 18:37:11][tgtg][notifiers.py:__init__:32][INFO] - Telegram: ['471886404']
[2025-03-02 18:37:11][tgtg][scanner.py:run:189][INFO] Sending test Notifications ...
[2025-03-02 18:37:21][tgtg][tgtg_client.py:_post:212][WARNING] Too many captcha Errors! Sleeping for 10 minutes...

scrapping every 40s

Shughen · 2025-03-02T18:39:15Z

I have just 2 favourites, and I'm getting troubles with recaptcha:

[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:289][INFO]   (__) \___/ (__) \___/  (____/ \___)\_/\_/\_)__)\_)__)(____)(__\_) 
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:290][INFO] 
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:291][INFO] Version 1.22.2
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:293][INFO] ©2025, Henning Merklinger
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:294][INFO] For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
[2025-03-02 18:29:46][tgtg][__main__.py:_print_welcome_message:295][INFO] 
[2025-03-02 18:29:48][tgtg][notifiers.py:__init__:28][INFO] Activated notifiers:
[2025-03-02 18:29:48][tgtg][notifiers.py:__init__:32][INFO] - Telegram: ['471886404']
[2025-03-02 18:29:48][tgtg][scanner.py:run:189][INFO] Sending test Notifications ...
[2025-03-02 18:29:57][tgtg][tgtg_client.py:_post:212][WARNING] Too many captcha Errors! Sleeping for 10 minutes...

and the same I get when I try to log in again:

[2025-03-02 18:37:05][tgtg][tgtg_client.py:start_polling:299][WARNING] Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
[2025-03-02 18:37:11][tgtg][tgtg_client.py:start_polling:305][INFO] Logged in!
[2025-03-02 18:37:11][tgtg][notifiers.py:__init__:28][INFO] Activated notifiers:
[2025-03-02 18:37:11][tgtg][notifiers.py:__init__:32][INFO] - Telegram: ['471886404']
[2025-03-02 18:37:11][tgtg][scanner.py:run:189][INFO] Sending test Notifications ...
[2025-03-02 18:37:21][tgtg][tgtg_client.py:_post:212][WARNING] Too many captcha Errors! Sleeping for 10 minutes...

scrapping every 40s

Same issue for me (I'm on Mac and I also tried to use a VPN) :

2025-03-02 19:37:42 INFO Loaded config from /Volumes/T7Shield/projets/tgtg/config.ini
2025-03-02 19:37:42 INFO ____ ___ ____ ___ ____ ___ __ __ _ __ _ ____ ____
2025-03-02 19:37:42 INFO (_ )/ )( _)/ ) / ) / ) / \ ( ( ( ( ( )( _ \
2025-03-02 19:37:42 INFO )( ( ( \ )( ( ( \ _ ( ( / / // / ) _) ) /
2025-03-02 19:37:42 INFO () _/ () __/ (/ _)_/_/_))_)__)(_)(___)
2025-03-02 19:37:42 INFO
2025-03-02 19:37:42 INFO Version 1.22.2
2025-03-02 19:37:42 INFO ©2025, Henning Merklinger
2025-03-02 19:37:42 INFO For documentation and support please visit https://github.com/Der-Henning/tgtg/wiki
2025-03-02 19:37:42 INFO
2025-03-02 19:37:42 INFO Starting login process ...
2025-03-02 19:37:43 WARNING Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-03-02 19:37:48 WARNING Check your mailbox on PC to continue... (Mailbox on mobile won't work, if you have installed tgtg app.)
2025-03-02 19:37:53 INFO Logged in!
2025-03-02 19:37:54 INFO Activated notifiers:
2025-03-02 19:37:54 INFO - Telegram: ['1835571750']
2025-03-02 19:37:54 INFO Sending test Notifications ...
2025-03-02 19:38:04 WARNING Too many captcha Errors! Sleeping for 10 minutes...

niklasdoerfler · 2025-03-02T19:12:23Z

It looks like tgtg implemented a kind of rate limit or blocking per IP or something. My ISP at home provides carrier-grade NAT for IPv4 and native IPv6. This means that multiple users or households share the same outgoing IPv4 address. IPv6 addresses however are unique per device and not shared between users.
For me, I have the tgtg scanner running on my homeserver inside a docker container (which only uses IPv4) and getting also those captcha errors there. But if I run the same version of the tgtg scanner directly on my PC (which prefers to use IPv6) then everything works fine.
I'm afraid there's not much we can do about this kind of blocking of ip addresses, except somehow solve the captchas or forcing the scanner to use IPv6 if available... :/

aldebaran54 · 2025-03-02T19:52:42Z

It works for me with the new version and after a rebuild of the docker image on my raspberry.

ihor-chaban · 2025-03-02T21:59:39Z

@niklasdoerfler I'm seeing a similar behavior now.
I tried running a bot on my cloud server (IPv4), where it used to work before, and it failed with a 403 error.
Even when I tried forwarding it through a VPN connection with several completely different IPs and locations (IPv4), it kept failing.
But then I tried to run the bot locally on my laptop and it worked (IPv6).
Then I tried to run it locally, through the same VPN I tried on the cloud server (IPv4), and it failed again.

upd. I also tried using some quite exotic VPN locations like Nigeria, Colombia, etc. where TGTG is not even available, so I doubt someone could have triggered the rate limit for these IPs before. But they all were IPv4 and they all failed.

oxamafia · 2025-03-02T22:22:57Z

I really think they implemented a way to block bots… is there a way to get the URL to solve the captcha?
And maybe resolve it automatically somehow?

Moley123 mentioned this issue Feb 26, 2025

The bot is not working with API auth errors #577

Open

c0lumb0 mentioned this issue Feb 27, 2025

HTTPError: Response code 404 () marklagendijk/node-toogoodtogo-watcher#258

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TGTG API Error: (404, b'') #579

TGTG API Error: (404, b'') #579

EtotheM commented Feb 26, 2025

nibbler75 commented Feb 26, 2025

vyskoczilova commented Feb 26, 2025

p3g4asus commented Feb 26, 2025

p3g4asus commented Feb 26, 2025

Der-Henning commented Feb 26, 2025 •

edited

Loading

steff94 commented Feb 26, 2025 •

edited

Loading

ihor-chaban commented Feb 27, 2025

p3g4asus commented Feb 27, 2025 •

edited

Loading

p3g4asus commented Feb 27, 2025

Der-Henning commented Feb 27, 2025 •

edited

Loading

p3g4asus commented Feb 27, 2025

ShotaArveladze24 commented Feb 27, 2025

niklasdoerfler commented Feb 27, 2025

p3g4asus commented Feb 27, 2025

p3g4asus commented Feb 27, 2025 •

edited

Loading

niklasdoerfler commented Feb 27, 2025

antonioli86 commented Feb 27, 2025 •

edited

Loading

ihor-chaban commented Feb 28, 2025 •

edited

Loading

p3g4asus commented Feb 28, 2025

Der-Henning commented Feb 28, 2025

steff94 commented Feb 28, 2025

Moley123 commented Feb 28, 2025

vyskoczilova commented Feb 28, 2025

ihor-chaban commented Feb 28, 2025 •

edited

Loading

ihor-chaban commented Feb 28, 2025 •

edited

Loading

ShotaArveladze24 commented Mar 1, 2025

p3g4asus commented Mar 1, 2025

vyskoczilova commented Mar 2, 2025 •

edited

Loading

Shughen commented Mar 2, 2025 •

edited

Loading

niklasdoerfler commented Mar 2, 2025

aldebaran54 commented Mar 2, 2025

ihor-chaban commented Mar 2, 2025 •

edited

Loading

oxamafia commented Mar 2, 2025

TGTG API Error: (404, b'') #579

TGTG API Error: (404, b'') #579

Comments

EtotheM commented Feb 26, 2025

nibbler75 commented Feb 26, 2025

vyskoczilova commented Feb 26, 2025

p3g4asus commented Feb 26, 2025

p3g4asus commented Feb 26, 2025

Der-Henning commented Feb 26, 2025 • edited Loading

steff94 commented Feb 26, 2025 • edited Loading

ihor-chaban commented Feb 27, 2025

p3g4asus commented Feb 27, 2025 • edited Loading

p3g4asus commented Feb 27, 2025

Der-Henning commented Feb 27, 2025 • edited Loading

p3g4asus commented Feb 27, 2025

ShotaArveladze24 commented Feb 27, 2025

niklasdoerfler commented Feb 27, 2025

p3g4asus commented Feb 27, 2025

p3g4asus commented Feb 27, 2025 • edited Loading

niklasdoerfler commented Feb 27, 2025

antonioli86 commented Feb 27, 2025 • edited Loading

ihor-chaban commented Feb 28, 2025 • edited Loading

p3g4asus commented Feb 28, 2025

Der-Henning commented Feb 28, 2025

steff94 commented Feb 28, 2025

Moley123 commented Feb 28, 2025

vyskoczilova commented Feb 28, 2025

ihor-chaban commented Feb 28, 2025 • edited Loading

ihor-chaban commented Feb 28, 2025 • edited Loading

ShotaArveladze24 commented Mar 1, 2025

p3g4asus commented Mar 1, 2025

vyskoczilova commented Mar 2, 2025 • edited Loading

Shughen commented Mar 2, 2025 • edited Loading

niklasdoerfler commented Mar 2, 2025

aldebaran54 commented Mar 2, 2025

ihor-chaban commented Mar 2, 2025 • edited Loading

oxamafia commented Mar 2, 2025

Der-Henning commented Feb 26, 2025 •

edited

Loading

steff94 commented Feb 26, 2025 •

edited

Loading

p3g4asus commented Feb 27, 2025 •

edited

Loading

Der-Henning commented Feb 27, 2025 •

edited

Loading

p3g4asus commented Feb 27, 2025 •

edited

Loading

antonioli86 commented Feb 27, 2025 •

edited

Loading

ihor-chaban commented Feb 28, 2025 •

edited

Loading

ihor-chaban commented Feb 28, 2025 •

edited

Loading

ihor-chaban commented Feb 28, 2025 •

edited

Loading

vyskoczilova commented Mar 2, 2025 •

edited

Loading

Shughen commented Mar 2, 2025 •

edited

Loading

ihor-chaban commented Mar 2, 2025 •

edited

Loading