Open davidegirardi opened 1 year ago
Same issue here - reverting to ddbbd42718b15172cdf409f2c1050362d42c3151
until further notice.
Thank you for this issue and your workaround!
You can run the latest version(s) with no issues if you run the workaround before running the playbook (or restart Synapse after running the queries).
Describe the bug Some of the bot users (mautrix-facebook, mautrix-telegram but not mautrix-discord in my case) are disabled in the DB and the new Synapse does not accept their logins.
To Reproduce
ddbbd42718b15172cdf409f2c1050362d42c3151
.ba868ba6c6d84c6ee1bf7e120bcce90ad6151d3b
at the time or writing)matrix-mautrix-telegram.service
andmatrix-mautrix-facebook.service
fail with the following error in the logs:mautrix.errors.request.MUserDeactivated: This account has been deactivated
Expected behavior The services running.
Matrix Server:
Workaround solution
As written in the room, I think the issue is with the new checks that Synapse does with regards to deactivated users. My workaround has been to just enable them in the DB before running the playbook at the last commit.