[bug] The Telegram notification channel on the Docker application is not working.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
Hello,
Thank you so much for creating such a great app.
This is the first time I've used it.
I'm deploying it self-hosted using Docker Compose.
Everything is working great, but Telegram notifications are not working. When I click test, it shows a red x icon.
I tried configuring the bot and chat ID on app-tianji.msgbyte.com and it works.
I noticed that the version I deployed on docker compose is your latest version v1.18.1, while on your cloud web is v1.17.4. Is that the difference?
I copied and used your exact compose file without any changes, except for JWT_SECRET.
Did I do anything wrong? Or is this a bug? I look forward to your review and check.
Thank you.
Have a nice day.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failed Telegram notification test in the Docker Compose deployment described in the issue, using version v1.18.1 and the provided compose file. Compare the self-hosted behavior with the working cloud configuration and trace the Telegram notification entry point; done means the test notification succeeds in the stated deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, typescript
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100