Skip to content

Conversation

@Sharparam
Copy link

Neither the GET nor POST variants of the Synapse /login API should be called when support for MSC4190 is enabled: https://areweoidcyet.com/

Fixes: mautrix/telegram#1020


I tested this by cloning the Telegram bridge locally and using my forked branch instead of the normal Mautrix library. After doing that I was able to once again use the local (non-public) address for my Synapse server and it correctly used the MSC4190 code instead of the /login endpoint. I was able to interact with Telegram normally from both the TG and Matrix sides.

Neither the GET nor POST variants of the Synapse `/login` API should
be called when support for MSC4190 is enabled: https://areweoidcyet.com/

Fixes: mautrix/telegram#1020
@Sharparam
Copy link
Author

Oops, didn't realise there was a PR for this already at #178. Closing this in favor of that one.

@Sharparam Sharparam closed this Aug 11, 2025
@Sharparam Sharparam deleted the msc4190-fix branch August 13, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Unable to connect to homeserver after setting up MAS

1 participant