You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Telegram API credentials don't seem to be working. A colleague is having the same issue, even though his API credentials are working with Telethon. Tried updating Telegram app, clearing cache, deleting and reinstalling. This is the error message:
'Cannot create a dataset with these parameters. An unexpected error (RPCError 406: UPDATE_APP_TO_LOGIN (caused by SendCodeRequest)) occurred and your authentication could not be verified.'
My friend is accessing 4CAT on his own Macbook using Docker. I have tried two instances both hosted on my university's servers. One is v1.39 (not using Docker) the other is v1.42 (using Docker).
The text was updated successfully, but these errors were encountered:
Yes, the issue is with the Telethon application/library. They seem to have addressed it and we will hopefully have a release soon using the newest version soon. Will update here when released.
We have incorporated Telethon's newest version in 4CAT and it will be in the next release. If you are using Docker, you can update you .env file and set DOCKER_TAG=latest, then follow the upgrade instructions to use our development version which has incorporated a newer version of Telethon. I believe this will fix your problem, but if not please let us know.
Telegram API credentials don't seem to be working. A colleague is having the same issue, even though his API credentials are working with Telethon. Tried updating Telegram app, clearing cache, deleting and reinstalling. This is the error message:
'Cannot create a dataset with these parameters. An unexpected error (RPCError 406: UPDATE_APP_TO_LOGIN (caused by SendCodeRequest)) occurred and your authentication could not be verified.'
My friend is accessing 4CAT on his own Macbook using Docker. I have tried two instances both hosted on my university's servers. One is v1.39 (not using Docker) the other is v1.42 (using Docker).
The text was updated successfully, but these errors were encountered: