fix: restart telegram bot after token upload (1.7.3)#32
Merged
Conversation
agentram
force-pushed
the
release/1.7.3
branch
2 times, most recently
from
23d847e to
3c37904
Compare
When a bot was already running, ovpn server monitor telegram-setup would deploy the bundle (force-recreating the container with the old on-disk token), write the new token file, then call monitor up without --force-recreate — leaving the bot running with the wrong token. Added RestartTelegramBotRemote in deploy.go that force-recreates ovpn-telegram-bot immediately after the token file is written. Also expanded Telegram setup docs with BotFather and @RawDataBot guidance. Bumps version to 1.7.3.
agentram
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ovpn server monitor telegram-setupnow force-recreates theovpn-telegram-botcontainer immediately after uploading the new token file. Previously the bot could start with the old on-disk token during the deploy step, and the subsequentmonitor upcall left it running with the wrong token since it doesn't use--force-recreate.docs/monitoring.mdTelegram setup section with step-by-step BotFather bot creation guide and a@RawDataBottip for finding your numeric owner user ID. Added brief hints toREADME.mdquickstart.1.7.3.Test plan
ovpn server monitor telegram-setup <server> --token <new-token> --owner-user-id <id>on a server where monitoring is already running with a different tokenovpn server logs <server> --service ovpn-telegram-botshows the bot polling successfully with nowatchdog_unhealthymetric