Discourse Chat Bridge (Telegram)

[dr460nf1r3 (Nιƈσ 🐉🔥)]

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.

Alter log level in Production?

If I understand things correctly it’s suppressing info and debug in production mode by design. Blaming logster/lib/logster/rails/railtie.rb at main · discourse/logster · GitHub store.level = Logger::Severity::WARN if Rails.env.production? From a blog post In production mode it aggregates similar errors by fingerprinting backtraces listening for warnings/errors and fatal messages. The intention is to display a list of open application problems that can somehow be resolved. In development mo…

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?

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

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.