Skip to content
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

HTTPError: Response code 403 #245

Open
polish96 opened this issue Oct 7, 2023 · 2 comments
Open

HTTPError: Response code 403 #245

polish96 opened this issue Oct 7, 2023 · 2 comments

Comments

@polish96
Copy link

polish96 commented Oct 7, 2023

When attempting to execute the application with the command toogoodtogo-watcher watch, I encounter this error message:

Error during request:
POST https://apptoogoodtogo.com/api/auth/v3/token/refresh
undefined

HTTPError: Response code 403 ()
    at Request.<anonymous> (file:///C:/Users/4851/AppData/Roaming/npm/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/as-promise/index.js:86:42)
    at Object.onceWrapper (node:events:629:26)
    at Request.emit (node:events:526:35)
    at Request._onResponseBase (file:///C:/Users/4851/AppData/Roaming/npm/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/core/index.js:727:22)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Request._onResponse (file:///C:/Users/4851/AppData/Roaming/npm/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/core/index.js:766:13)

To solve the problem, I tried uninstalling Node.js and then reinstalling it. Next, I installed the application using npm install -g toogoodtogo-watcher and modified the "config" file according to the instructions using toogoodtogo-watcher config. Then, I logged in using toogoodtogo-watcher login --email mail@example.com and confirmed the link that was sent to my email. The login process was successful. However, despite all these steps, the same error message continues to appear.

@polish96
Copy link
Author

Yesterday, the application started working automatically, and new notifications were coming in. However, since this morning, an error message has been displayed again, and there are no new notifications.

@c0lumb0
Copy link

c0lumb0 commented Jan 4, 2024

I encountered the same error message, more or less.
It then disappeared for some days and notifications were working just fine and now they are appearing again for the 2nd day in a row.

This reminds me of

#212
#201

I think it is related to datadome protection again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants