Discourse Chat Bridge (Telegram)

Lhc_fl · 11월 20, 2023, 1:37오전

Ok, I fixed this.

Lhc_fl · 12월 22, 2023, 7:11오전

The bridge plugin has is now compatible with the latest discourse test-passed version.

Monikas · 3월 26, 2024, 12:46오전

I’m looking forward to it supporting QQ afterwards

Altair · 12월 13, 2024, 9:29오전

As I understand from the latest messages in the topic: the plugin is functioning. Please tell me if I am right in this assumption.

May I ask if this plugin works with telegram themes (chat sections)?

Thank you very much for your work

Moin · 12월 13, 2024, 9:35오전

Welcome to Meta

The latest posts were written before the latest edit to the first post, where the broken tag was added, happened.

So, I would expect that it’s still broken.

Lhc_fl · 1월 20, 2025, 2:21오후

I’m glad to announce that this plugin is now compatible agian with the latest version of Discourse

kOS · 1월 25, 2025, 3:35오후

love this. I dont use Telegram, but I love the opportunity that this project will allow us to integrate with Matrix finally <3

dr460nf1r3 · 1월 25, 2025, 8:22오후

Is there a way to obtain logs of the plugin? @Lhc_fl
I’m trying to figure out why it only works one way (Discourse → Telegram). Bot of course has permission to access group messages. There are no apparent logs in the console

Edit: was trying to troubleshoot this, and seemingly it is basically impossible to get proper logs in production.

Not even errors or warnings related to the plugin are logged in production.log / production_error.log.

I’m suspecting some webhook related issue, and from the looks the plugin doesn’t get deactivated on errors?

github.com/Lhcfl/discourse-chat-bridge

lib/chat_bridge_module/provider/telegram/services/setup_webhook.rb

main


      
                    cid, gid, tok = config.split(",")
                    raise "Not valid config" if (cid.nil? || gid.nil? || tok.nil?)
                    cid
                  end
                  .uniq
                  .each do |cid|
                    bot = ::ChatBridgeModule::Provider::Telegram::TelegramBot.new(cid)
                    response = bot._request("setWebhook", message)
                    if response["ok"] != true
                      # If setting up webhook failed, disable provider
                      # SiteSetting.chat_bridge_enabled = false
                      Rails.logger.error(
                        "Failed to setup telegram webhook for chat channel #{cid}. Message data= " +
                          message.to_json + " response=" + response.to_json,
                      )
                    end
                  end
              end
            end
          end

As it works one way the credentials provided are definitely correct. If someone has an idea how to obtain the logs written by the plugin, please let me know.

Lhc_fl · 1월 26, 2025, 10:31오전

It’s just supressing INFO and DEBUG, I’m pretty confident that Rails.logger.error will leave error logs in production Other logs are by design not supposed to appear in production.

I wrote this plugin a long time ago, maybe I should probably check its webhook logic.

Lhc_fl · 1월 26, 2025, 10:43오전

Try accessing this URL in your browser and see what the output is?

https://api.telegram.org/bot{token}/setWebhook?url=https://your.discourse.site/chat-bridge/telegram/hook/123456

Replace {token} with your bot token.

If the webhook is set up correctly, it should receive a ok message.

dr460nf1r3 · 1월 26, 2025, 10:45오전

Yep, I can confirm that this works:

{"ok":true,"result":true,"description":"Webhook was set"}

Lhc_fl · 1월 26, 2025, 10:52오전

That’s strange. And if the creation of the message fails, the error log will be printed here, you should be able to see it in https://your.discourse.site/logs

github.com/Lhcfl/discourse-chat-bridge

lib/chat_bridge_module/provider/telegram/bridge.rb

main


      
          
              Scheduler::Defer.later("Bridge a telegram #{event} to discourse") do
                result =
                  ::ChatBridgeModule::Provider::Telegram::Services::HandleTgMessage.call(
                    params: {
                      message:,
                      edit: event == :edited_message,
                    },
                  )
          
                Rails.logger.error(<<~TEXT) if result.failure?
                    [Telegram Bridge] Failed to bridge message:
                    #{result.inspect_steps}
                    TEXT
              end
            end
          end
          
          # Discourse ---> Telegram
          %i[chat_message_created chat_message_edited chat_message_trashed].each do |event|
            DiscourseEvent.on(event) do |message, channel, user| # rubocop:disable Discourse/Plugins/UsePluginInstanceOn

Could it really be a permissions issue? If reply directly to the bridged message created by the telegram bot, will it succeed?

dr460nf1r3 · 1월 26, 2025, 11:55오전

I’m in fact seeing now a few logs related to the module in /logs:

[Discourse -> Telegram] Failed in chat_message_created: 
Inspecting ChatBridgeModule::Provider::Telegram::Services::HandleDiscourseMessage result object:

[1/8] [params] default (0.0555 ms) ✅
[2/8] [model] bot (0.0178 ms) ✅
[3/8] [step] ensure_bot_valid ❌

(5 more steps not shown as the execution flow was stopped before reaching them)

Why it failed:

INVALID_BOT

activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:130:in `block in warn'

activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `block in dispatch'

activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `each'

activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `dispatch'

activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:130:in `warn'

/var/www/discourse/plugins/discourse-chat-bridge/lib/chat_bridge_module/provider/telegram/bridge.rb:51:in `block (3 levels) in <main>'

/var/www/discourse/lib/scheduler/defer.rb:125:in `block in do_work'

rails_multisite-6.1.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'

rails_multisite-6.1.0/lib/rails_multisite/connection_management.rb:21:in `with_connection'

/var/www/discourse/lib/scheduler/defer.rb:119:in `do_work'

/var/www/discourse/lib/scheduler/defer.rb:105:in `block (2 levels) in start_thread'

But thats from yesterday and didn’t repeat afterwards, so I’m assuming it had to do with adding the bot and not meeting all requirements yet. After that, nore more bridge plugin logs. Unless, of course, that caused it to never work after that

No, that does not work.

I wonder whether its possible to look into the secret created by the plugin, as this would allow manual creation?

I just noticed one thing while looking through Nginx logs (as the webhook call must occur here)

[26/Jan/2025:12:05:39 +0000] "forum.xyz.org" 91.108.5.109 "POST /chat-bridge/telegram/hook/123456 HTTP/1.1" "-" "chat_bridge_module/telegram_webhook/hook" 403 5865 "-" 0.009 0.010 "-" "-" "-" "-" "-" "-" "-"

That’s the webhook I manually created earlier right?

… and we are one step further. I manually set the secret path via rails console and adapted the webhook manually. POST request to Discouse now succeeds. And now there is an actual error:

/var/www/discourse/plugins/discourse-chat-bridge/lib/chat_bridge_module/provider/telegram/services/handle_tg_message.rb:110:in `message_creation_succeed'

/var/www/discourse/lib/service/base.rb:156:in `instance_exec'

/var/www/discourse/lib/service/base.rb:156:in `run_step'

/var/www/discourse/lib/service/base.rb:199:in `run_step'

/var/www/discourse/lib/service/base.rb:139:in `block in call'

/var/www/discourse/lib/service/base.rb:165:in `with_runtime'

/var/www/discourse/lib/service/base.rb:139:in `call'

/var/www/discourse/lib/service/base.rb:457:in `block in run!'

/var/www/discourse/lib/service/base.rb:457:in `each'

/var/www/discourse/lib/service/base.rb:457:in `run!'

/var/www/discourse/lib/service/base.rb:450:in `run'

<internal:kernel>:90:in `tap'

/var/www/discourse/lib/service/base.rb:302:in `call'

/var/www/discourse/plugins/discourse-chat-bridge/lib/chat_bridge_module/provider/telegram/bridge.rb:9:in `block (3 levels) in <main>'

/var/www/discourse/lib/scheduler/defer.rb:125:in `block in do_work'

rails_multisite-6.1.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'

rails_multisite-6.1.0/lib/rails_multisite/connection_management.rb:21:in `with_connection'

/var/www/discourse/lib/scheduler/defer.rb:119:in `do_work'

/var/www/discourse/lib/scheduler/defer.rb:105:in `block (2 levels) in start_thread'

Job exception: In params.message creation: Inspecting Chat::CreateMessage result object:

[ 1/28] [options] default (0.0168 ms) ✅
[ 2/28] [policy] no_silenced_user (0.0148 ms) ✅
[ 3/28] [policy] accept_blocks (0.0051 ms) ✅
[ 4/28] [params] default (0.0742 ms) ✅
[ 5/28] [model] channel (0.7018 ms) ✅
[ 6/28] [step] enforce_membership (0.013 ms) ✅
[ 7/28] [model] membership ❌

(21 more steps not shown as the execution flow was stopped before reaching them)

Why it failed:

/var/www/discourse/lib/service/base.rb:184:in `run_step': Model not found (ArgumentError)

          raise ArgumentError, "Model not found"
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
	from /var/www/discourse/lib/service/base.rb:139:in `block in call'
	from /var/www/discourse/lib/service/base.rb:165:in `with_runtime'
	from /var/www/discourse/lib/service/base.rb:139:in `call'
	from /var/www/discourse/lib/service/base.rb:457:in `block in run!'
	from /var/www/discourse/lib/service/base.rb:457:in `each'
	from /var/www/discourse/lib/service/base.rb:457:in `run!'
	from /var/www/discourse/lib/service/base.rb:450:in `run'
	from <internal:kernel>:90:in `tap'
	from /var/www/discourse/lib/service/base.rb:302:in `call'
	from /var/www/discourse/plugins/discourse-chat-bridge/lib/chat_bridge_module/provider/telegram/services/handle_tg_message.rb:91:in `fetch_message_creation'
	from /var/www/discourse/lib/service/base.rb:156:in `instance_exec'
	from /var/www/discourse/lib/service/base.rb:156:in `run_step'
	from /var/www/discourse/lib/service/base.rb:182:in `run_step'
	from /var/www/discourse/lib/service/base.rb:139:in `block in call'
	from /var/www/discourse/lib/service/base.rb:165:in `with_runtime'
	from /var/www/discourse/lib/service/base.rb:139:in `call'
	from /var/www/discourse/lib/service/base.rb:457:in `block in run!'
	from /var/www/discourse/lib/service/base.rb:457:in `each'
	from /var/www/discourse/lib/service/base.rb:457:in `run!'
	from /var/www/discourse/lib/service/base.rb:450:in `run'
	from <interna...

But this looks more like a configuration issue I wonder why I need to adjust.

Lhc_fl · 1월 26, 2025, 12:17오후

Oh, this is not expected, I guess I made a mistake here when adapting to the new version of Discourse. Will take a look at it

dr460nf1r3 · 1월 26, 2025, 12:18오후

Thank you! Let me know if there is anything I can do to help.

dr460nf1r3 · 6월 3, 2025, 4:43오후

Hey @Lhc_fl I wanted to kindly ask whether there are still plans of fixing this

dr460nf1r3 · 7월 14, 2026, 3:45오후

플러그인을 포크하고 수정했습니다. 이제 예상대로 작동합니다. 이것이 올바른 방법이었기를 바랍니다!

merefield · 7월 14, 2026, 5:28오후

이제 메인 저장소에 PR을 보내는 것을 고려해볼 수 있으며, 리뷰 과정에서 알게 될지도 모릅니다

dr460nf1r3 · 7월 14, 2026, 6:26오후

방금 이 작업을 완료했습니다. 저장소와 확장 기능이 매우 방치된 상태라 그전까지는 신경 쓰지 않았습니다.

merefield · 7월 14, 2026, 6:36오후

네, 공감이 갑니다. 그건 문제가 될 수 있죠. 다만 OP는 한때 아주 활동적이었거든요 …

글		댓글	조회수
Discourse-Telegram chat bridge Plugin chat-integration , chat	0	143	7월 7, 2026
Discourse Chat Integrations Plugin official , chat-integration , included-in-core	22	103720	4월 21, 2026
Telegram Notifications Plugin (discourse-telegram-notifications) Plugin	85	29370	5월 2, 2026
Set up Telegram integration using the discourse-chat-integration plugin Integrations chat-integration , how-to	92	19510	10월 31, 2025
Discord Bot Construction Kit :robot: Plugin pavilion	139	23016	6월 13, 2024

Discourse Chat Bridge (Telegram)

Related topics