Hi,
I have PRTG set up to send REST API calls to an external messaging system via the Execute HTTP action notification.
This all worked well for weeks, until last week it stopped and the problem appears to be in PRTG, possibly around SSL. If I hit the same URL in Chrome on the server the message is delivered, but in PRTG it is not. Is there debugging/logs or a cache or anything I can use to try and fix this? The server does send a text response for each hit.
Thanks
Add comment