[telegram_bot] Invalid secret token from $ip_address about core

[Urbanus-Ursus]

Maybe this is because HA is installed behind Nginx which is used as Reverse Proxy?

[home-assistant]

telegram_bot documentation
telegram_bot source

[wilcomir]

I have tried to manually send a message to the relevant group chat via curl:

     -H 'Content-Type: application/json' \
     -d '{"chat_id": "123456789", "text": "This is a test from curl", "disable_notification": true}' \
     https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendMessage```
     
and it works just fine, I get back an ok response and the message arrives to the chat.

[wilcomir]

Restarting homeassistant fixes the issue, I have just tried. I suspect this might have something to do with the fact that I use the cloudflare add on to expose my instance to the internet. In the past I had a fixed public IP and exposed my instance via a reverse proxy & port forwarding, now that is not true anymore but this has changed a few months ago so I am not sure how the two can be connected.

[Urbanus-Ursus]

I have the exact same problem. I can't figure out what's going on. I understand that when you start working in WebHook mode, some handshake happens and Secret Token is negotiated. And it seems that after some time (or some number of messages) this token is incorrectly reinstalled. I can't determine at what moment it happens.

[wilcomir]

I am running my homeassistant instance through the cloudflare add on. Not sure why it would have an impact - perhaps webhooks work via ip, and not fqdn? That would be rather odd though, and many more people would have this problem.