-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 on token refresh #115
Comments
same here, something is off with captcha returning |
yeah, login process is still broken for me too, i guess this only fixes fetching items when there is a valid session available |
I found that toogoodtoogo may ban your IP if you used node-toogoodtogo-watcher before on the same IP, using a fresh new IP solve the issue. |
Right (tested on my dedicated), unfortunatly, i used it on Docker from my NAS, i have fiber, with fix IP (even when i reboot router :( ) |
I am in fiber with fixed IP too, and changing IP would not be trivial because it is accredited for my teleworking activity ... Can we just hope that the address will be released in ... days / month / years ? |
wow, I was wrong. Did not realize that in fact my ipv4 address was burned, and my v6 is fine. Tried to 'unblock' my v4 by passing valid cookies |
Switching to version 3.7.0 this morning: it works! Phew, I'm not going to need to get my IP released (I was trying to contact them via a friend of the neighbor's daughter, that's my desperation) Thank you ! |
I still get the same error with 3.7.0.
|
What auth api are you using?
post("auth/v2/loginByEmail"
Op zo 14 nov. 2021 10:53 schreef Fran Torres ***@***.***>:
… I still get the same error with 3.7.0.
Do you think it is the IP?
Error during request:
POST https://apptoogoodtogo.com/api/auth/v2/token/refresh
{
"refresh_token": "TOKEN"
}
HTTPError: Response code 403 (Forbidden)
at Request.<anonymous> (/usr/lib/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/as-promise/index.js:117:42)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGDRTQAT35VZP5GFSBYJBTUL6BJLANCNFSM5H6S74HA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Have You tried connecting to different ip address? |
Have you tried the "device_type": "ANDROID"?
.post("auth/v2/loginByEmail", {
json: {
device_type: "ANDROID",
Le dim. 14 nov. 2021 à 13:15, andrzejpodgorny ***@***.***> a
écrit :
… Hello I still have a 403 error with the last version after the PR for #112
<#112>
and #113
<#113>
toogoodtogo-watcher_1 | Error during request:
toogoodtogo-watcher_1 | POST https://apptoogoodtogo.com/api/auth/v2/loginByEmail
toogoodtogo-watcher_1 <https://apptoogoodtogo.com/api/auth/v2/loginByEmailtoogoodtogo-watcher_1> | {
toogoodtogo-watcher_1 | "device_type": "UNKNOWN",
toogoodtogo-watcher_1 | "email": "*****",
toogoodtogo-watcher_1 | "password": "*****"
toogoodtogo-watcher_1 | }
toogoodtogo-watcher_1 |
toogoodtogo-watcher_1 | HTTPError: Response code 403 (Forbidden)
toogoodtogo-watcher_1 | at Request.<anonymous> (/home/node/app/node_modules/got/dist/source/as-promise/index.js:117:42)
toogoodtogo-watcher_1 | at processTicksAndRejections (internal/process/task_queues.js:95:5)
When I try to POST on Insomnia I obtain this response asking me to resolve
a captcha
<html><head><title>apptoogoodtogo.com</title><style>#cmsg{animation: A ***@***.*** A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style></head><body style="margin:0"><p id="cmsg">Please enable JS and disable any ad blocker</p><script>var dd={'cid':'AHrlqAAAAAMANoQuwp2NxI8ATZMnzg==','hsh':'1D42C2CA6131C526E09F294FE96F94','t':'fe','r':'b','s':35702,'host':'geo.captcha-delivery.com'}</script><script src="https://ct.captcha-delivery.com/c.js"></script></body></html>
Maybe we can re-open #114
<#114>?
You tried connecting to different ip address?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGDRTU75YBDQONYPBNXZKLUL6R5HANCNFSM5H6S74HA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I'm having the same issue, going to check the device_type as mentioend by @navimondo |
@andrzejpodgorny Thanks, will try that one |
@navimondo @andrzejpodgorny That one worked, I will create PR |
Created PR #116 |
Alright, I spoke too fast, it only worked for one day : Error during request: HTTPError: Response code 403 (Forbidden) hopeless |
I am having the same problem. |
This bot works for me. The changes I made are: Change this line: node-toogoodtogo-watcher/lib/api.js Line 35 in 3e6f680
to: device_type: credentials.device_type and place in your config.json this:
I know it can be done nicer, in a more programmatic way, but I don't want to change it anymore :) |
@andrzejpodgorny |
the developer, can get inspired can be here: https://github.com/MoterHaker/bypass-captcha-examples @Fratorhe With IP modify via connection sharing same problem (dynamic ip) |
I won't accept any CATPCHA-bypassing PRs, please see #118. |
here it bypasses by generating a token. : |
No, he just implemented using the refresh token. This application already used that from the start. |
Last version solved this issue for me. Thanks. The last 3 days my tgtg-watcher was complety shutted down, maybe my IP is released for a couple of hours. If there is a new captcha issue, see #118 |
Hello
I still have a 403 error with the last version after the PR for #112 and #113
When I try to POST on Insomnia I obtain this response asking me to resolve a captcha
Maybe we can re-open #114?
The text was updated successfully, but these errors were encountered: