Fixed
Group / topic setup silently broken
The bot would post update notifications into a group / topic just fine, but every command got dropped and every button click came back with "not authorised". The cause: the auth check compared from.id (the clicker's personal user ID) against CHAT_ID — but in a group, CHAT_ID is the group ID (often negative, -100…). The two could never match outside a 1:1 chat.
Now compares chat.id (origin chat) instead. Works for 1:1 chats, regular groups, and forum groups with topics.
Reported by @jayjay3108 in #2.
Added
TELEGRAM_ALLOWED_USERS whitelist
Optional env var / Web UI field. Comma-separated list of Telegram user IDs allowed to control the bot. Empty = anyone in the configured chat (right default for 1:1). In a group, set this to lock down /cleanup, "Update all", etc. to specific members.
environment:
- CHAT_ID=-1001234567890 # group ID
- TELEGRAM_ALLOWED_USERS=11111111,22222222Debug-mode logging on auth failure
With DEBUG=true (or the Web UI toggle), auth rejections now print the reason — mismatched chat.id, or user not in whitelist. Silent in non-debug to avoid log spam from drive-by messages in shared groups.
README: Group / Topic setup section
Step-by-step for running Docksentry in a Telegram group with topics, including the @BotFather → /setprivacy → Disable step that's easy to miss.
docker pull amayer1983/docksentry:latest
docker compose up -d