Hello everyone, I have the PRTG version 22.4.81.1532 installed. an error appears during HTTP Action.

EIdHTTPProtocolException: HTTP/1.1 400 Bad Request.

I also have an older version of PRTG 19.4.54.1506 installed Everything works on this version, there are no errors.

HTTP Action. I use it to send notifications to telegram chat.

https://api.telegram.org/<bottoken>/sendMessage
Do not send SNI (default)

chat_id=-<chatid>&text=
There's a *%status* sensor in your PRTG!
[%device](%linksensor)

HTTP 1.1 (default)

Article Comments

Hello,

can you check out this article? Check your SNI configuration. I suspect SNI+FQDN issues. https://helpdesk.paessler.com/en/support/solutions/articles/76000063166-my-http-sensors-fail-to-monitor-websites-which-use-sni-what-can-i-do

Good luck!


Jan, 2023 - Permalink

Hello Roman,

in this case the Bad Request is coming from Telegram trying to decode the placeholder values in the "Test Notification" function as UTF-8 Characters and failing. The Full error Telegram is reporting back is: {"ok":false,"error_code":400,"description":"Bad Request: text must be encoded in UTF-8"}

To verify the function please simulate an error on a sensor (right-click > "Simulate Error Status", afterwards don't forget to resume the sensor) that is set up for this notification template to properly test the notification.
Usually it works despite the "Test notification" function failing.

Kind regards,
Johannes Beyerlein, Technical Support Team


Jan, 2023 - Permalink

Hi, Johannes

thank you very much, I tried it as you said, so everything works. error only when I try to send test notification.


Jan, 2023 - Permalink

Hello Roman,

Thank you for the feedback. Glad it worked out.

Kind regards,
Johannes Beyerlein, Technical Support Team


Jan, 2023 - Permalink

I had the exact same problem with the exact same PRTG version and Telegram. Seems like it is the %device parameter that Telegram chokes on. If I remove that, the test works.

However - the real notifications gets send, so its ok after all.


Mar, 2023 - Permalink

Hello Rolf,

Yes this is an issue inside the Telegram API misinterpreting the %placeholder messages as control message and therefore failing, in the real notification those get replace by their respective values and therefore work without a problem.

Kind regards,
Johannes Beyerlein, Technical Support Team


Mar, 2023 - Permalink