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.

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

mautrix-telegram bridge (v0.15.2) throws an error 'This message is not supported on your version of Mautrix-Telegram' #982

Open
lgp171188 opened this issue Dec 17, 2024 · 0 comments

Comments

@lgp171188
Copy link

I run my own Matrix homeserver (using https://github.com/spantaleev/matrix-docker-ansible-deploy) and use the mautrix-telegram bridge (version: v0.15.2. Thanks for making great software!). In some Telegram channels that I am in, the bridge reports the

This message is not supported on your version of Mautrix-Telegram. Please check https://github.com/mautrix/telegram or ask your bridge administrator about possible updates.

error message for some messages instead of the actual message.

{
  "type": "m.room.message",
  "room_id": "!cwlADovSbPmHcraxvB:lgp.sh",
  "sender": "@telegram_31272138:lgp.sh",
  "content": {
    "msgtype": "m.notice",
    "body": "This message is not supported on your version of Mautrix-Telegram. Please check https://github.com/mautrix/telegram or ask your bridge administrator about possible updates.",
    "external_url": "https://t.me/fossunited/35250",
    "fi.mau.telegram.unsupported": true,
    "fi.mau.telegram.source": {
      "space": 1162377025,
      "chat_id": 1162377025,
      "peer_type": "channel",
      "id": 35250
    }
  },
  "origin_server_ts": 1668147292000,
  "unsigned": {
    "membership": "join",
    "age": 66295072194
  },
  "event_id": "$B-nJy-YFcXJrN_-jkfY2N7EPIYNmZUY3N1-ZNYN0Zy4",
  "user_id": "@telegram_31272138:lgp.sh",
  "age": 66295072194
}

This happens for some messages from some users, but not all their messages. So I suspect that this might be due to missing support in the bridge for the Telegram features used in these messages?

This error appears to be different from the one reported in #942, which was fixed in v0.15.2, that I already run.

Please let me know if any additional information is needed to investigate this further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant