MHSanaei 93ff60e568 fix(tgbot): reload bot on settings save so a new token takes effect without a panel restart ...

The Telegram bot was only started at panel boot, so saving a token or toggling tgBotEnable persisted to the DB but never reached the running bot until a full restart, making it look like the token did not save (issue #5539). The settings/update controller now reconciles the bot the same way panelOutbound reconciles Xray: when tgBotEnable, the token, chat ID, or API server change, it stops/(re)starts the bot and updates the event-bus subscription.

2026-06-24 17:34:05 +02:00

9.4 KiB

Raw Blame History

View Raw