-
Notifications
You must be signed in to change notification settings - Fork 117
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
Telegram Login Error #223
Comments
I have same problem but got error code 400 |
Same issue here! Tried also with command line login and get:
|
HTTP 403 is the error code for "forbidden", means the host blocked your request. This often happens when your IP is temp banned for sending too many requests or failing the bot check. Did you update to the latest version that supports the datadome cookies? |
@basti1499 I did update to latest version and always get this issue as well, so this looks more like a permanent ban more than a temporary one (maybe the bot check is failing). I am using a private server not a cloud environment. |
Can you try opening If you get HTTP error 405 you're good, then your IP is not being blocked. What kind of server are you using? Hosted at home or in some data center? |
@basti1499 If I open the refresh page sometimes I get 405 directly and sometimes the captcha; anyway, even after solving it, I am still unable to login via telegram bot (same error as original reporter). I am using a Ubuntu server in office and opening tgtg website from a laptop in the same LAN, with same public IP. |
I'd suggest to turn the bot off for a few hours/days and check whether the captcha check went away. Can you run a browser instance on your server and solve the captcha there? This might trigger tgtg to send your server the necessary datadome cookie. |
@basti1499 Tried with a browser instance on same server, solved the captcha and got again same login error trough telegram bot. |
Then maybe it's time to let the bot rest a few days :) |
@basti1499 the watcher has been shut down since my first post on this issue (2 weeks ago) up to this afternoon but yet no luck :( |
Oh, then I don't really know what else you could try. |
Another idea, did you try to fully uninstall the bot and start from scratch? Maybe some old config/cookie is hanging somewhere... |
@basti1499 I am running the watcher as a Docker container; I have tried to tier down and recreate it many times, even with a brand new config file but I always get the same behaviour. Here is my config file for reference: {
"api": {
"credentials": {
"email": "YYYYYYYYY"
},
"session": {},
"deviceType": "IOS",
"headers": {},
"pollingIntervalInMs": 30000,
"authenticationIntervalInMS": 3600000
},
"notifications": {
"console": {
"enabled": false,
"clear": true
},
"desktop": {
"enabled": false
},
"telegram": {
"enabled": true,
"botToken": "XXXXXXXXX",
"chats": [
{
"id": -00000000,
"firstName": "Andrea",
"lastName": "Vida"
}
]
},
"apprise": {
"enabled": false,
"host": "apprise:8080",
"services": [
{
"url": "Any Apprise Notification service URL. Example: mailto://domain.com?user=userid&pass=password. See https://github.com/caronc/apprise#table-of-contents",
"format": "The message format, as supported by this notification service. Can be `html`, `text`"
}
]
}
},
"messageFilter": {
"showUnchanged": false,
"showDecrease": false,
"showDecreaseToZero": false,
"showIncrease": false,
"showIncreaseFromZero": true
}
} |
Hi,
Telegram Bot gets error after command "/login email".
Something went wrong "HTTPError: Response code 403 ()\n at Request.<anonymous> (file:///usr/lib/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/as-promise/index.js:86:42)\n at Object.onceWrapper (node:events:627:26)\n at Request.emit (node:events:524:35)\n at Request._onResponseBase (file:///usr/lib/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/core/index.js:726:22)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Request._onResponse (file:///usr/lib/node_modules/toogoodtogo-watcher/node_modules/got/dist/source/core/index.js:765:13)"
The text was updated successfully, but these errors were encountered: