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

..

config

v3.4.0

2026-06-23 17:45:36 +02:00

database

feat(iplimit): gate IP limit on fail2ban and reset stale limits

2026-06-22 23:15:58 +02:00

eventbus

perf: prevent cron job overlap, auto-set GOMEMLIMIT, fix tgbot userStates race

2026-06-22 02:48:58 +02:00

logger

refactor(frontend): move form-item hints from extra to tooltip

2026-06-17 17:24:16 +02:00

mtproto

refactor(frontend): move form-item hints from extra to tooltip

2026-06-17 17:24:16 +02:00

sub

fix(sub): drive display remarks from the template and split multi-host subpage links

2026-06-24 16:45:23 +02:00

util

perf: prevent cron job overlap, auto-set GOMEMLIMIT, fix tgbot userStates race

2026-06-22 02:48:58 +02:00

web

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

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

xray

Use efficient APIs and simplify loops

2026-06-23 14:12:28 +02:00