The Telegram bot's config (enable flag, token, proxy, API server) was read only during a full server.Start(). The in-process "Restart Panel" path (StopPanelOnly/StartPanelOnly -> stop/start with the bot flag false) skipped the bot entirely, so enabling the bot or changing its proxy did not take effect until a full OS-level `systemctl restart x-ui`. Cycle the Telegram bot in the panel-only restart path while still leaving Xray and the traffic writer untouched (preserving the #4265 freeze fix), so "Restart Panel" reconciles the bot with the latest settings. Fixes #5033 |
||
|---|---|---|
| .. | ||
| controller | ||
| entity | ||
| global | ||
| job | ||
| locale | ||
| middleware | ||
| network | ||
| runtime | ||
| service | ||
| session | ||
| translation | ||
| websocket | ||
| web.go | ||