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.

Sign up for GitHub

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

Jump to bottom

Sometimes startup cannot complete due to 1 account being stuck trying to connect to Telegram #316

Open
turt2live opened this issue Apr 20, 2019 · 0 comments · May be fixed by #698
Open

Sometimes startup cannot complete due to 1 account being stuck trying to connect to Telegram #316

turt2live opened this issue Apr 20, 2019 · 0 comments · May be fixed by #698
Labels
bug: defect Something isn't working and it never has worked

Comments

@turt2live
Copy link
Contributor

Usually restarting the bridge a few times will get it unstuck, however at 157 puppets to connect to Telegram the bridge often gets stuck at one of them, preventing the others from starting and preventing the appservice web listener from starting.

There's no consistent reason for it getting stuck, unfortunately:

  • Sometimes telethon gets stuck in a reconnect loop (fix is to restart - there's no recovering from this I've found)
  • Sometimes nothing happens at all - the user's telegram ID doesn't show up in the logs
  • Sometimes it looks like it connected okay, but for some reason hasn't moved on. Possibly unable to get chat listing or taking too long?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug: defect Something isn't working and it never has worked
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Connect Telegram users after startup lazily to avoid slow startup times Half-Shot/mautrix-telegram
2 participants
@turt2live @tulir