telegram icon indicating copy to clipboard operation
telegram copied to clipboard

Bridge stops working after a random amount of time

Open LaT3St opened this issue 2 years ago • 1 comments

mautrix-telegram_1 | [2022-08-31 10:41:27,930] [[email protected]] Server sent a very new message with ID [PRIVATE?], ignoring mautrix-telegram_1 | [2022-08-31 10:41:27,930] [[email protected]] Security error while unpacking a received message: Too many messages had to be ignored consecutively

This happens every time i receive or send a message to Telegram via the bridge. The bridge just stops working without an apparent reason. This happened a few times now. The only fix known to me is to delete the database and reconfigure bridging.

I logged out of Telegram via the bot during the debug process. The bot ignores other commands like "help" or "login". If i send "logout" again, the bot responds correctly that I'm not logged in.

LaT3St avatar Aug 31 '22 10:08 LaT3St

same here

clown139880 avatar Sep 08 '22 05:09 clown139880

Today I updated to Version 0.12.1 of the Bridge (Docker Container) and see the same behaviour. Log messages like described by the OP and the bot is not responding to any commands except logout. It also will print the error message if I type an unknown command, but no valid command does anything.

seiichiro0185 avatar Sep 28 '22 18:09 seiichiro0185

Update: It seems the Problem in my case was the wrong time of the Server running the bridge. After (re-) activating NTP Timesync on the Server it now works as expected again.

seiichiro0185 avatar Sep 30 '22 06:09 seiichiro0185

Thanks for your comment. My bridge works since i did the same to my server. I've checked the time on the server before resyncing. It was a few seconds behind global time.

I suggest adding some sort of error message at least as a few seconds time difference should not break the whole bridge.

LaT3St avatar Oct 25 '22 11:10 LaT3St