Messages not showing up in channels but showing up in group and personal chats

[laurensmiers]

Hi,

I have synapse and mautrix-telegram (together with some other bridges (whatsapp, signal, ...) running in docker-compose. For testing, I disabled the other bridges to get some clean logs later in this post.

The bridge was working fine until some days ago. Direct/private messages and group messages were working fine.
However, I stopped being able to see group messages, direct/private messaging is still working fine.
Strangely, if I look in the logs of the mautrx-telegram docker, it seems to be syncing/finding messages fine.

Something that is probably easier to debug and is already suspicious that it isn't working as expected is the telegram-bridge-bot.
I tested sending messages to the telegram bridge bot directly but I don't get any response from it either (meaning I don't see it in the matrix client).
I do see in the mautrix-telegram/synapse docker logs that it gets my message (f.e. 'help') and it does send a reply back, so everything looks ok.

I tried several clients: element, nheko, fluffy, neochat, ... but they all have the same behaviour.
It might be a client issue since the logs state the message 'help' is received and its response is being send back, if I understand correctly; but since the behaviour is consistent with several clients, I'm wondering if it is a server-side issue.
Also worth noting, I don't see this behaviour with other bridges (whatsapp, signal, ...) .

Anyone seen this behaviour before or any ideas what might cause this?

Thanks in advance!

FYI:

• synapse logs of the 'help' message to the telegram-bridge bot:

[2022-09-28 08:17:09,473] [DEBUG@mau.as] Finished handling transaction 111138,
[2022-09-28 08:17:09,472] [DEBUG@mau.as] Handling transaction 111138 with 1 EDUs,
[2022-09-28 08:17:09,476] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:09 +0000] "PUT /transactions/111138?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:10,747] [DEBUG@mau.as] Handling transaction 111139 with 1 EDUs,
[2022-09-28 08:17:10,749] [DEBUG@mau.as] Finished handling transaction 111139,
[2022-09-28 08:17:10,752] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:10 +0000] "PUT /transactions/111139?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:11,045] [DEBUG@mau.as] Handling transaction 111140 with 1 PDUs,
[2022-09-28 08:17:11,048] [DEBUG@mau.as] Finished handling transaction 111140,
[2022-09-28 08:17:11,052] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:11 +0000] "PUT /transactions/111140?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:11,054] [DEBUG@mau.mx] Received Matrix event $k0wPFyrQCEHw44ibDqCNwHgSGqvIcKDG-XA2f5VKRRA from @myuser:mymatrix.xyz in !RVdMufpvyZLdTIlLQr:mymatrix.xyz,
[2022-09-28 08:17:11,070] [DEBUG@mau.as.api.bot] req #18: GET http://synapse:8008/_matrix/client/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/joined_members?user_id=@telegrambot:mymatrix.xyz None,
[2022-09-28 08:17:11,087] [DEBUG@mau.as.api.bot] req #18 (/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/joined_members) completed in 15.9ms with status 200,
[2022-09-28 08:17:11,219] [DEBUG@mau.as.api.bot] req #19: PUT http://synapse:8008/_matrix/client/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/send/m.room.message/mautrix-python_1664353031218156918_7?user_id=@telegrambot:mymatrix.xyz {"msgtype": "m.notice", "body": "This is a management room: prefixing commands with `!tg` is not required.\n#### General\n**cancel**  - Cancel an ongoing action.  \n**version**  - Get the bridge version.  \n**help**  - Show this help message.  \n\n#### Authentication\n**login-matrix**  - Replace your Telegram account's Matrix puppet with your own Matrix account.  \n**logout-matrix**  - Disable double puppeting.  \n**ping-matrix**  - Pings the Matrix server with the double puppet.  \n**clear-cache-matrix**  - Clear the Matrix sync token stored for your double puppet.  \n**username** <_new username_> - Change your Telegram username.  \n**about** <_new about_> - Change your Telegram about section.  \n**displayname** <_new displayname_> - Change your Telegram displayname.  \n**session** <`list`|`terminate`> [_hash_] - View or delete other Telegram sessions.  \n**ping**  - Check if you're logged into Telegram.  \n**ping-bot**  - Get the info of the message relay Telegram bot.  \n**register** <_phone_> <_full name_> - Register to Telegram  \n**login-qr**  - Log in by scanning a QR code.  \n**login**  - Get instructions on how to log in.  \n**logout**  - Log out from Telegram.  \n\n#### Creating portals\n**bridge** [_id_] - Bridge the current Matrix room to the Telegram chat with the given ID. The ID must be the prefixed version that you get with the `/id` command of the Telegram-side bot.  \n**create** [_type_] - Create a Telegram chat of the given type for the current Matrix room. The type is either `group`, `supergroup` or `channel` (defaults to `supergroup`).  \n**pm** <_identifier_> - Open a private chat with the given Telegram user. The identifier is either the internal user ID, the username or the phone number. **N.B.** The phone numbers you start chats with must already be in your contacts.  \n**join** <_link_> - Join a chat with an invite link.  \n\n#### Portal management\n**delete-portal**  - Remove all users from the current portal room and forget the portal. Only works for group chats; to delete a private chat portal, simply leave the room.  \n**unbridge**  - Remove puppets from the current portal room and forget the portal.  \n**config** <`help`|_subcommand_> [...] - View or change per-portal settings.  \n**invite-link** [--uses=<amount>] [--expire=<time delta, e.g. 1d>] [--request-needed] -- [title] - Get a Telegram invite link to the current chat.  \n**list-invite-links** [creator] - List existing Telegram invite links to the current chat.  \n**upgrade**  - Upgrade a normal Telegram group to a supergroup.  \n**group-name** <_name_|`-`> - Change the username of a supergroup/channel. To disable, use a dash (`-`) as the name.  \n**backfill** [_limit_] - Backfill messages from Telegram history.  \n\n#### Miscellaneous\n**sync-state**  - Fetch Matrix room state to ensure the bridge has up-to-date info.  \n**id**  - Get the ID of the Telegram chat where this room is bridged.  \n**caption** <_caption_> - Set a caption for the next image you send  \n**search** [_-r|--remote_] <_query_> - Search your contacts or the Telegram servers for users.  \n**sync** [`chats`|`contacts`|`me`] - Synchronize your chat portals, contacts and/or own info.  \n**play** <_play ID_> - Play a Telegram game.  \n**vote** <_poll ID_> <_choice number_> - Vote in a Telegram poll.  \n**random** <_emoji_> - Roll a dice (\ud83c\udfb2), kick a football (\u26bd\ufe0f) or throw a dart (\ud83c\udfaf) or basketball (\ud83c\udfc0) on the Telegram servers.  \n", "format": "org.matrix.custom.html", "formatted_body": "<p>This is a management room: prefixing commands with <code>!tg</code> is not required.</p>\n<h4>General</h4>\n<p><strong>cancel</strong>  - Cancel an ongoing action.<br />\n<strong>version</strong>  - Get the bridge version.<br />\n<strong>help</strong>  - Show this help message.</p>\n<h4>Authentication</h4>\n<p><strong>login-matrix</strong>  - Replace your Telegram account's Matrix puppet with your own Matrix account.<br />\n<strong>logout-matrix</strong>  - Disable double puppeting.<br />\n<strong>ping-matrix</strong>  - Pings the Matrix server with the double puppet.<br />\n<strong>clear-cache-matrix</strong>  - Clear the Matrix sync token stored for your double puppet.<br />\n<strong>username</strong> &lt;<em>new username</em>&gt; - Change your Telegram username.<br />\n<strong>about</strong> &lt;<em>new about</em>&gt; - Change your Telegram about section.<br />\n<strong>displayname</strong> &lt;<em>new displayname</em>&gt; - Change your Telegram displayname.<br />\n<strong>session</strong> &lt;<code>list</code>|<code>terminate</code>&gt; [<em>hash</em>] - View or delete other Telegram sessions.<br />\n<strong>ping</strong>  - Check if you're logged into Telegram.<br />\n<strong>ping-bot</strong>  - Get the info of the message relay Telegram bot.<br />\n<strong>register</strong> &lt;<em>phone</em>&gt; &lt;<em>full name</em>&gt; - Register to Telegram<br />\n<strong>login-qr</strong>  - Log in by scanning a QR code.<br />\n<strong>login</strong>  - Get instructions on how to log in.<br />\n<strong>logout</strong>  - Log out from Telegram.</p>\n<h4>Creating portals</h4>\n<p><strong>bridge</strong> [<em>id</em>] - Bridge the current Matrix room to the Telegram chat with the given ID. The ID must be the prefixed version that you get with the <code>/id</code> command of the Telegram-side bot.<br />\n<strong>create</strong> [<em>type</em>] - Create a Telegram chat of the given type for the current Matrix room. The type is either <code>group</code>, <code>supergroup</code> or <code>channel</code> (defaults to <code>supergroup</code>).<br />\n<strong>pm</strong> &lt;<em>identifier</em>&gt; - Open a private chat with the given Telegram user. The identifier is either the internal user ID, the username or the phone number. <strong>N.B.</strong> The phone numbers you start chats with must already be in your contacts.<br />\n<strong>join</strong> &lt;<em>link</em>&gt; - Join a chat with an invite link.</p>\n<h4>Portal management</h4>\n<p><strong>delete-portal</strong>  - Remove all users from the current portal room and forget the portal. Only works for group chats; to delete a private chat portal, simply leave the room.<br />\n<strong>unbridge</strong>  - Remove puppets from the current portal room and forget the portal.<br />\n<strong>config</strong> &lt;<code>help</code>|<em>subcommand</em>&gt; [...] - View or change per-portal settings.<br />\n<strong>invite-link</strong> [--uses=&lt;amount&gt;] [--expire=&lt;time delta, e.g. 1d&gt;] [--request-needed] -- [title] - Get a Telegram invite link to the current chat.<br />\n<strong>list-invite-links</strong> [creator] - List existing Telegram invite links to the current chat.<br />\n<strong>upgrade</strong>  - Upgrade a normal Telegram group to a supergroup.<br />\n<strong>group-name</strong> &lt;<em>name</em>|<code>-</code>&gt; - Change the username of a supergroup/channel. To disable, use a dash (<code>-</code>) as the name.<br />\n<strong>backfill</strong> [<em>limit</em>] - Backfill messages from Telegram history.</p>\n<h4>Miscellaneous</h4>\n<p><strong>sync-state</strong>  - Fetch Matrix room state to ensure the bridge has up-to-date info.<br />\n<strong>id</strong>  - Get the ID of the Telegram chat where this room is bridged.<br />\n<strong>caption</strong> &lt;<em>caption</em>&gt; - Set a caption for the next image you send<br />\n<strong>search</strong> [<em>-r|--remote</em>] &lt;<em>query</em>&gt; - Search your contacts or the Telegram servers for users.<br />\n<strong>sync</strong> [<code>chats</code>|<code>contacts</code>|<code>me</code>] - Synchronize your chat portals, contacts and/or own info.<br />\n<strong>play</strong> &lt;<em>play ID</em>&gt; - Play a Telegram game.<br />\n<strong>vote</strong> &lt;<em>poll ID</em>&gt; &lt;<em>choice number</em>&gt; - Vote in a Telegram poll.<br />\n<strong>random</strong> &lt;<em>emoji</em>&gt; - Roll a dice (\ud83c\udfb2), kick a football (\u26bd\ufe0f) or throw a dart (\ud83c\udfaf) or basketball (\ud83c\udfc0) on the Telegram servers.</p>\n"},
[2022-09-28 08:17:11,481] [DEBUG@mau.as.api.bot] req #19 (/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/send/m.room.message/mautrix-python_1664353031218156918_7) completed in 261.4ms with status 200,
[2022-09-28 08:17:11,579] [DEBUG@mau.as] Handling transaction 111141 with 1 PDUs,
[2022-09-28 08:17:11,581] [DEBUG@mau.as] Finished handling transaction 111141,
[2022-09-28 08:17:11,583] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:11 +0000] "PUT /transactions/111141?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0"

• Mautrix-telegram logs of the 'help' message to the telegram-bridge bot:

[2022-09-28 08:17:09,473] [DEBUG@mau.as] Finished handling transaction 111138,
[2022-09-28 08:17:09,472] [DEBUG@mau.as] Handling transaction 111138 with 1 EDUs,
[2022-09-28 08:17:09,476] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:09 +0000] "PUT /transactions/111138?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:10,747] [DEBUG@mau.as] Handling transaction 111139 with 1 EDUs,
[2022-09-28 08:17:10,749] [DEBUG@mau.as] Finished handling transaction 111139,
[2022-09-28 08:17:10,752] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:10 +0000] "PUT /transactions/111139?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:11,045] [DEBUG@mau.as] Handling transaction 111140 with 1 PDUs,
[2022-09-28 08:17:11,048] [DEBUG@mau.as] Finished handling transaction 111140,
[2022-09-28 08:17:11,052] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:11 +0000] "PUT /transactions/111140?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0",
[2022-09-28 08:17:11,054] [DEBUG@mau.mx] Received Matrix event $k0wPFyrQCEHw44ibDqCNwHgSGqvIcKDG-XA2f5VKRRA from @myuser:mymatrix.xyz in !RVdMufpvyZLdTIlLQr:mymatrix.xyz,
[2022-09-28 08:17:11,070] [DEBUG@mau.as.api.bot] req #18: GET http://synapse:8008/_matrix/client/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/joined_members?user_id=@telegrambot:mymatrix.xyz None,
[2022-09-28 08:17:11,087] [DEBUG@mau.as.api.bot] req #18 (/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/joined_members) completed in 15.9ms with status 200,
[2022-09-28 08:17:11,219] [DEBUG@mau.as.api.bot] req #19: PUT http://synapse:8008/_matrix/client/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/send/m.room.message/mautrix-python_1664353031218156918_7?user_id=@telegrambot:mymatrix.xyz {"msgtype": "m.notice", "body": "This is a management room: prefixing commands with `!tg` is not required.\n#### General\n**cancel**  - Cancel an ongoing action.  \n**version**  - Get the bridge version.  \n**help**  - Show this help message.  \n\n#### Authentication\n**login-matrix**  - Replace your Telegram account's Matrix puppet with your own Matrix account.  \n**logout-matrix**  - Disable double puppeting.  \n**ping-matrix**  - Pings the Matrix server with the double puppet.  \n**clear-cache-matrix**  - Clear the Matrix sync token stored for your double puppet.  \n**username** <_new username_> - Change your Telegram username.  \n**about** <_new about_> - Change your Telegram about section.  \n**displayname** <_new displayname_> - Change your Telegram displayname.  \n**session** <`list`|`terminate`> [_hash_] - View or delete other Telegram sessions.  \n**ping**  - Check if you're logged into Telegram.  \n**ping-bot**  - Get the info of the message relay Telegram bot.  \n**register** <_phone_> <_full name_> - Register to Telegram  \n**login-qr**  - Log in by scanning a QR code.  \n**login**  - Get instructions on how to log in.  \n**logout**  - Log out from Telegram.  \n\n#### Creating portals\n**bridge** [_id_] - Bridge the current Matrix room to the Telegram chat with the given ID. The ID must be the prefixed version that you get with the `/id` command of the Telegram-side bot.  \n**create** [_type_] - Create a Telegram chat of the given type for the current Matrix room. The type is either `group`, `supergroup` or `channel` (defaults to `supergroup`).  \n**pm** <_identifier_> - Open a private chat with the given Telegram user. The identifier is either the internal user ID, the username or the phone number. **N.B.** The phone numbers you start chats with must already be in your contacts.  \n**join** <_link_> - Join a chat with an invite link.  \n\n#### Portal management\n**delete-portal**  - Remove all users from the current portal room and forget the portal. Only works for group chats; to delete a private chat portal, simply leave the room.  \n**unbridge**  - Remove puppets from the current portal room and forget the portal.  \n**config** <`help`|_subcommand_> [...] - View or change per-portal settings.  \n**invite-link** [--uses=<amount>] [--expire=<time delta, e.g. 1d>] [--request-needed] -- [title] - Get a Telegram invite link to the current chat.  \n**list-invite-links** [creator] - List existing Telegram invite links to the current chat.  \n**upgrade**  - Upgrade a normal Telegram group to a supergroup.  \n**group-name** <_name_|`-`> - Change the username of a supergroup/channel. To disable, use a dash (`-`) as the name.  \n**backfill** [_limit_] - Backfill messages from Telegram history.  \n\n#### Miscellaneous\n**sync-state**  - Fetch Matrix room state to ensure the bridge has up-to-date info.  \n**id**  - Get the ID of the Telegram chat where this room is bridged.  \n**caption** <_caption_> - Set a caption for the next image you send  \n**search** [_-r|--remote_] <_query_> - Search your contacts or the Telegram servers for users.  \n**sync** [`chats`|`contacts`|`me`] - Synchronize your chat portals, contacts and/or own info.  \n**play** <_play ID_> - Play a Telegram game.  \n**vote** <_poll ID_> <_choice number_> - Vote in a Telegram poll.  \n**random** <_emoji_> - Roll a dice (\ud83c\udfb2), kick a football (\u26bd\ufe0f) or throw a dart (\ud83c\udfaf) or basketball (\ud83c\udfc0) on the Telegram servers.  \n", "format": "org.matrix.custom.html", "formatted_body": "<p>This is a management room: prefixing commands with <code>!tg</code> is not required.</p>\n<h4>General</h4>\n<p><strong>cancel</strong>  - Cancel an ongoing action.<br />\n<strong>version</strong>  - Get the bridge version.<br />\n<strong>help</strong>  - Show this help message.</p>\n<h4>Authentication</h4>\n<p><strong>login-matrix</strong>  - Replace your Telegram account's Matrix puppet with your own Matrix account.<br />\n<strong>logout-matrix</strong>  - Disable double puppeting.<br />\n<strong>ping-matrix</strong>  - Pings the Matrix server with the double puppet.<br />\n<strong>clear-cache-matrix</strong>  - Clear the Matrix sync token stored for your double puppet.<br />\n<strong>username</strong> &lt;<em>new username</em>&gt; - Change your Telegram username.<br />\n<strong>about</strong> &lt;<em>new about</em>&gt; - Change your Telegram about section.<br />\n<strong>displayname</strong> &lt;<em>new displayname</em>&gt; - Change your Telegram displayname.<br />\n<strong>session</strong> &lt;<code>list</code>|<code>terminate</code>&gt; [<em>hash</em>] - View or delete other Telegram sessions.<br />\n<strong>ping</strong>  - Check if you're logged into Telegram.<br />\n<strong>ping-bot</strong>  - Get the info of the message relay Telegram bot.<br />\n<strong>register</strong> &lt;<em>phone</em>&gt; &lt;<em>full name</em>&gt; - Register to Telegram<br />\n<strong>login-qr</strong>  - Log in by scanning a QR code.<br />\n<strong>login</strong>  - Get instructions on how to log in.<br />\n<strong>logout</strong>  - Log out from Telegram.</p>\n<h4>Creating portals</h4>\n<p><strong>bridge</strong> [<em>id</em>] - Bridge the current Matrix room to the Telegram chat with the given ID. The ID must be the prefixed version that you get with the <code>/id</code> command of the Telegram-side bot.<br />\n<strong>create</strong> [<em>type</em>] - Create a Telegram chat of the given type for the current Matrix room. The type is either <code>group</code>, <code>supergroup</code> or <code>channel</code> (defaults to <code>supergroup</code>).<br />\n<strong>pm</strong> &lt;<em>identifier</em>&gt; - Open a private chat with the given Telegram user. The identifier is either the internal user ID, the username or the phone number. <strong>N.B.</strong> The phone numbers you start chats with must already be in your contacts.<br />\n<strong>join</strong> &lt;<em>link</em>&gt; - Join a chat with an invite link.</p>\n<h4>Portal management</h4>\n<p><strong>delete-portal</strong>  - Remove all users from the current portal room and forget the portal. Only works for group chats; to delete a private chat portal, simply leave the room.<br />\n<strong>unbridge</strong>  - Remove puppets from the current portal room and forget the portal.<br />\n<strong>config</strong> &lt;<code>help</code>|<em>subcommand</em>&gt; [...] - View or change per-portal settings.<br />\n<strong>invite-link</strong> [--uses=&lt;amount&gt;] [--expire=&lt;time delta, e.g. 1d&gt;] [--request-needed] -- [title] - Get a Telegram invite link to the current chat.<br />\n<strong>list-invite-links</strong> [creator] - List existing Telegram invite links to the current chat.<br />\n<strong>upgrade</strong>  - Upgrade a normal Telegram group to a supergroup.<br />\n<strong>group-name</strong> &lt;<em>name</em>|<code>-</code>&gt; - Change the username of a supergroup/channel. To disable, use a dash (<code>-</code>) as the name.<br />\n<strong>backfill</strong> [<em>limit</em>] - Backfill messages from Telegram history.</p>\n<h4>Miscellaneous</h4>\n<p><strong>sync-state</strong>  - Fetch Matrix room state to ensure the bridge has up-to-date info.<br />\n<strong>id</strong>  - Get the ID of the Telegram chat where this room is bridged.<br />\n<strong>caption</strong> &lt;<em>caption</em>&gt; - Set a caption for the next image you send<br />\n<strong>search</strong> [<em>-r|--remote</em>] &lt;<em>query</em>&gt; - Search your contacts or the Telegram servers for users.<br />\n<strong>sync</strong> [<code>chats</code>|<code>contacts</code>|<code>me</code>] - Synchronize your chat portals, contacts and/or own info.<br />\n<strong>play</strong> &lt;<em>play ID</em>&gt; - Play a Telegram game.<br />\n<strong>vote</strong> &lt;<em>poll ID</em>&gt; &lt;<em>choice number</em>&gt; - Vote in a Telegram poll.<br />\n<strong>random</strong> &lt;<em>emoji</em>&gt; - Roll a dice (\ud83c\udfb2), kick a football (\u26bd\ufe0f) or throw a dart (\ud83c\udfaf) or basketball (\ud83c\udfc0) on the Telegram servers.</p>\n"},
[2022-09-28 08:17:11,481] [DEBUG@mau.as.api.bot] req #19 (/v3/rooms/%21RVdMufpvyZLdTIlLQr%3Amymatrix.xyz/send/m.room.message/mautrix-python_1664353031218156918_7) completed in 261.4ms with status 200,
[2022-09-28 08:17:11,579] [DEBUG@mau.as] Handling transaction 111141 with 1 PDUs,
[2022-09-28 08:17:11,581] [DEBUG@mau.as] Finished handling transaction 111141,
[2022-09-28 08:17:11,583] [INFO@aiohttp.access] 172.22.0.3 [28/Sep/2022:08:17:11 +0000] "PUT /transactions/111141?access_token=6gJJB6-bz_U-dlqvd37vZAKmmmngunAOm69WB3ApnjjBnR4DBiSMhlSi6pkCPGOQ HTTP/1.1" 200 159 "-" "Synapse/1.68.0"

[Photowalk]

Got the same problem here, I'm using element both on PC and Android. Have the matrix installed on my VPS 12 hours ago with ansible.

I can send messages to Telegram and Telegram can get the message, but the messages sent from Telegram didn't show up on element.

Rebooting the server(or matrix service maybe) can solve the problem temporarily, but after serveral hours or so, it went back to the same one-way communication situation.

[laurensmiers]

I changed the title to be more specific, didn't know about telegram channel 'types'. But it seems the channels (were only one person/admin can send) are not working anymore. The telegram-bridge is receiving and syncing them properly (I see new messages coming in from those channel types) but I'm not receiving them in any matrix client.

[Janbong]

I'm having the same problem, but with mautrix-whatsapp. Responses from the bot show up in the logs but never arrive in any Matrix client.

[tulir]

Usually happens if you ignore the bridge bot (channel messages are sent by the bot, normal messages are sent by ghost users)