# Telegram Notification Bug

**URL:** <https://discourse.crowdsec.net/t/telegram-notification-bug/1268>\
**Category:** Uncategorized\
**Created:** [April 27, 2023, 1:42pm UTC](https://discourse.crowdsec.net/t/telegram-notification-bug/1268 "2023-04-27T13:42:28Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![ScreN](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@ScreN](https://discourse.crowdsec.net/u/ScreN)\
**Post date:** [May 9, 2023, 11:28am UTC](https://discourse.crowdsec.net/t/telegram-notification-bug/1268/17 "2023-05-09T11:28:17Z")

</div>

Compose Stack.  
Traefik - CrowdSec - Bouncer-traefik

cscli version

```auto
2023/05/09 11:25:56 version: v1.4.6-5f71037b40c498045e1b59923504469e2b8d0140
2023/05/09 11:25:56 Codename: alphaga
2023/05/09 11:25:56 BuildDate: 2023-02-09_14:37:12
2023/05/09 11:25:56 GoVersion: 1.19.5
2023/05/09 11:25:56 Platform: linux
2023/05/09 11:25:56 Constraint_parser: >= 1.0, <= 2.0
2023/05/09 11:25:56 Constraint_scenario: >= 1.0, < 3.0
2023/05/09 11:25:56 Constraint_api: v1
2023/05/09 11:25:56 Constraint_acquis: >= 1.0, < 2.0

```

Telegram works fine with other containers. The problem is only with CrowdSec Notifications

---

_[View the full topic](https://discourse.crowdsec.net/t/telegram-notification-bug/1268)._