Telegram notification

[nbctcp]

SW INFO:
-pnetlab 5.2.7

-fortigate qcow eval license

https://www.youtube.com/watch?v=26_2A9YOjdc

https://www.youtube.com/watch?v=ND8JTAwkoQM

I am following above links to set notification in telegram if admin login

I can send manually from linux to telegram

# curl --request 'POST'https://api.telegram.org/bot5962153123:AAHf7wKYu7dhheSiLc580pC4G-LUmEvOSLA/sendMessage -H 'Content-Type:application/json' -d '{"chat_id":"-759260123","text":"coba2"}' 

CONFIG:
config system automation-action
edit "telegram"
set action-type webhook
set protocol https
set uri "api.telegram.org/bot5962153123:AAHf7wKYu7dhheSiLc580pC4G-LUmEvOSLA/sendMessage"
set http-body "{\"chat_id\":\"-759260123\",\"text\":\"%%msg%%\"}"
set port 443
set headers "Content-Type:application/json"
set verify-host-cert enable
next
end

STATUS:
-I can see System Event shown "Automation stitch triggered" but nothing happen in my telegram

?
1. can I test using fortigate 7.2 eval license in pnetlab

tq

UPDATE1:

-with real 80D I can get notif in telegram

that mean I can't test webhook in vm eval license

[pminarik · Accepted solution]

Just an educated guess: Make a packet capture of traffic going to the api.telegram.org address, and then check the pcap. Pay attention to the TLS handshake first.

The trial VMs are known to have severely restricted crypto algorithms, to the point of being unfit for modern use. While an exception has been made for incoming admin access and FortiManager communication (ref ), I would assume that outgoing stitches are still bound by these restrictions. The pcap should allow you to verify this - if the TLS handshake is failing due to no crypto match, that's it.