Open stfnnklv opened 4 years ago
can confirm this, did not "matrix-logout" before logging out of telegram. now after logging in to telegram i am not able to do "matrix-login": access token is not valid. the same access token works for mautrix-whatsapp though.
on startup of the bridge i get:
Apr 01 05:11:52 mautrix-telegram[10186]: [2020-04-01 05:11:52,895] [ERROR@mau.puppet.51752300] Failed to initialize custom mxid
Apr 01 05:11:52 mautrix-telegram[10186]: Traceback (most recent call last):
Apr 01 05:11:52 mautrix-telegram[10186]: File "/opt/synapse/lib/python3.7/site-packages/mautrix/bridge/custom_puppet.py", line 165, in try_start
Apr 01 05:11:52 mautrix-telegram[10186]: await self.start()
Apr 01 05:11:52 mautrix-telegram[10186]: File "/opt/synapse/lib/python3.7/site-packages/mautrix/bridge/custom_puppet.py", line 186, in start
Apr 01 05:11:52 mautrix-telegram[10186]: raise InvalidAccessToken()
any news on this?
I'm also getting stray occurrences of this. In the logs:
[2020-05-05 23:18:30,891] [ERROR@mau.user.@user:stratum0.org] Failed to automatically enable custom puppet
Traceback (most recent call last):
File "/home/matrix/mautrix-telegram-0.7.1/mautrix_telegram/user.py", line 213, in post_login
await puppet.switch_mxid(access_token="auto", mxid=self.mxid)
File "/home/matrix/matrix-appservice-tg/lib/python3.7/site-packages/mautrix/bridge/custom_puppet.py", line 152, in switch_mxid
await self.start()
File "/home/matrix/matrix-appservice-tg/lib/python3.7/site-packages/mautrix/bridge/custom_puppet.py", line 186, in start
raise InvalidAccessToken()
In chats, not only does double puppeting break but telegram messages are reflected back to matrix after they are (correctly) posted to telegram.
Hello,
With double puppeting enabled, in case the access token becomes invalid, the bridge continues to try to use it, throwing warnings and errors in the log, but neither attempts to login again (if login_shared_secret is enabled) or logout completely. If the bridge process is restarted and login_shared_secret is enabled, the access token is regenerated and double puppeting is working fine again. If you send "ping-matrix" command to the bot, it replies with "Your access token is invalid.". If you "ping-matrix" again, the reply is "You are not logged in with your Matrix account.", although the access_token and custom_mxid remain in the puppet table in the database. So after the process is restarted, they are loaded again. Before that restart, everything behaves as if double puppeting is disabled.
Please find relevant logs:
After restart of the process:
If you decide to "ping-matrix" twice:
Kind regards, Stefan Nikolov