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

[telegram-api] RPCError while login #1901

Closed
Malcom3D opened this issue Dec 3, 2021 · 0 comments
Closed

[telegram-api] RPCError while login #1901

Malcom3D opened this issue Dec 3, 2021 · 0 comments
Assignees

Comments

@Malcom3D
Copy link

Malcom3D commented Dec 3, 2021

Step 1: Have you search for this issue before posting it?

yes

Step 2: Describe your environment

  • OS : Linux
  • Python Version: 3.8.12
  • In case you are not using a binary version:
    • Branch: Master
    • Last Commit ID: c80ed22

Step 3: Describe the problem:

Describe the bug
Telegram Api Service fail to connect with the error described in this Telethon issue.
Was fixed with telethon version 1.24 some day ago, but octobot-services requires telethon 1.23

Expected behavior
Telegram Api Service connect without error.

Steps to reproduce:

  1. if you don't already have it, create a new configuration for telegram-api.
  2. save and restart Octobot.
  3. check the logs for TelegramApiService ERROR.

Observed Results:

  • What happened?
    Telegram Api Service return error on login.

  • What did you expect to happen?
    Telegram Api Service login without errors.

Relevant code exceptions or logs:

2021-12-03 23:54:37,643 ERROR TelegramApiService Failed to connect to Telegram Api : RPCError 406: UPDATE_APP_TO_LOGIN (caused by SendCodeRequest)
2021-12-03 23:54:37,645 ERROR TelegramApiService Error when connecting to Telegram API ('NoneType' object has no attribute 'username'): invalid telegram configuration.
2021-12-03 23:54:37,645 WARNING ServiceFactory TelegramApiService initial checkup failed.
2021-12-03 23:54:37,646 WARNING TelegramApiServiceFeed Impossible to start TelegramApiServiceFeed: required service TelegramApiService is not available.
2021-12-03 23:54:37,647 ERROR OctoBotChannelServiceConsumer Failed to start TelegramApiServiceFeed. Evaluators requiring this service feed might not work properly.

@Herklos Herklos self-assigned this Jan 2, 2022
Herklos added a commit to Drakkar-Software/OctoBot-Services that referenced this issue Jan 2, 2022
Herklos added a commit to Drakkar-Software/OctoBot-Services that referenced this issue Jan 2, 2022
@Herklos Herklos closed this as completed Jan 2, 2022
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