Telegram notification not working

[rj10rd]

When update available or container updated there is no notification recieved on telegram

[scttbnsn]

Hey @rj10rd 👋 — a few things to check:

1. Verify your env vars are set correctly

You need at minimum:

DD_TRIGGER_TELEGRAM_{name}_BOTTOKEN=your-bot-token
DD_TRIGGER_TELEGRAM_{name}_CHATID=your-chat-id

Replace {name} with any label you want (e.g. 1, MYBOT, etc.).

2. Check the logs

Look for these in your Drydock logs:

• Register all components of kind trigger for provider telegram — confirms the trigger loaded
• Registering for auto execution with component: trigger.telegram.* — confirms it will fire automatically
• Any WARN or ERROR lines mentioning trigger.telegram — these would show API errors from Telegram

3. Common issues

• Wrong chat ID — make sure you're using the numeric chat ID, not the username. For groups, the ID is negative (e.g. -1001234567890). You can get it from the Telegram Bot API getUpdates endpoint after sending a message to your bot.
• Bot not added to group — if using a group chat, the bot must be a member of that group.
• Bot token format — should look like 123456789:AABBccDDeeFF... (number, colon, alphanumeric string).
• once: true (default) — triggers only fire once per container update. If you've already seen the update in the UI but the trigger errored on the first attempt, it won't retry. Restart Drydock to reset.

Could you share:

1. Your Telegram-related environment variables (redact the bot token)
2. The relevant log output from startup and after a scan completes

Docs for reference: https://getdrydock.com/docs/configuration/triggers/telegram

[rj10rd]

Sir i want to talk you personally 😊

[scttbnsn]

No need my friend! Thank you for hanging out!

[rj10rd]

Thanks sir but my wedding on 21 april so I am busy and I want only to invite you on wedding. thank for this awesome app i give feedback after my wedding but telegram notification not working.

[scttbnsn]

@rj10rd Congratulations on your wedding! 🎉 We would love to come!

Good news — we found and fixed the Telegram notification bug. The issue was that MarkdownV2 special characters in container names and version numbers (dots, dashes, parentheses, etc.) were not being escaped in the message body, which caused the Telegram API to reject the message with a 400 error. So your trigger was configured correctly — it was a bug on our side.

The fix is shipping in RC2 which is going out today. Once you're back from celebrating, update to the latest version and your Telegram notifications should just work.

Enjoy the wedding! We'll be here when you're ready. 🥂

[rj10rd]

[scttbnsn]

Fixed in v1.5.0. Root cause: MarkdownV2 reserved characters — dots, dashes, and parens in container and tag names — weren't being escaped before being passed to Telegram. Fix covers both trigger() and triggerBatch() paths. Closing.

[scttbnsn]

@rj10rd First — belated congratulations to you and your wife! 🎉 I hope your April 21 wedding and the celebrations went beautifully. Thank you for coming back, and I’m sorry Telegram is still not working for you.

I checked the code and release history before replying. The MarkdownV2 fix is still present and unchanged in v1.5.0, v1.5.1, and v1.5.2-rc.4, and the Telegram provider tests pass. So I do not want to guess that this is the same bug without seeing where delivery fails.

Could you please send these three things?

1. The exact Drydock version shown in the UI or startup log (for example v1.5.1 or v1.5.2-rc.4).
2. Your Telegram environment-variable names with the bot token completely redacted. Please do not post the token.
3. The trigger.telegram startup line and the WARN/ERROR line produced after an update or a manual test.

One useful diagnostic: temporarily set DD_TRIGGER_TELEGRAM_<NAME>_MESSAGEFORMAT=HTML, restart Drydock, and test again. If HTML works, we have found another Markdown formatting case. If HTML also fails, we can focus on trigger registration, the bot/chat, or connectivity instead. Also confirm that you have sent /start to the bot.

We will keep this open until we get Telegram working for you.

[ciltocruz]

Telegram notifications works correctly.
This photo is yesterday

[rj10rd]

Please give me your full env value of telegram notification.
And what version are you using.

[ciltocruz]

Version 1.6.0-rc.1 (but works since 1.4.0)

My env:

• DD_NOTIFICATION_TELEGRAM_1_BOTTOKEN=${DD_NOTIFICATION_TELEGRAM_BOTTOKEN}
• DD_NOTIFICATION_TELEGRAM_1_CHATID=${DD_NOTIFICATION_TELEGRAM_CHATID}
• DD_NOTIFICATION_TELEGRAM_1_MODE=digest
• DD_NOTIFICATION_TELEGRAM_1_MESSAGEFORMAT=HTML

DD_NOTIFICATION_TELEGRAM_BOTTOKEN and DD_NOTIFICATION_TELEGRAM_CHATID are my variables for secret values.

[rj10rd]

Thank you sir i am not using this env DD_NOTIFICATION_TELEGRAM_1_MESSAGEFORMAT=HTML

[ciltocruz]

Test it and share your comments