I have created a notification to send a http action (to OpsGenie for SMS, and push notifications) but I'm unable to get it to work. I've looked in the notification logs and get the following error:

--------------------------------------------------------------------------------------------------------------------------- Failed to establish secure connection [Step 0] Error connecting with SSL. Error connecting with SSL. error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure [Step 1] Error connecting with SSL. Error connecting with SSL. error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure [Step 2] Error connecting with SSL. Error connecting with SSL. error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure [Step 3] Error connecting with SSL. Error connecting with SSL. error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure [Step 4] Error connecting with SSL. Error connecting with SSL. error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure [Step 5] Socket Error # 10054 Connection reset by peer. [Unsecure] IOHandler value is not valid ---------------------------------------------------------------------------------------------------------------------------

Using Postman in Chrome I am able to send a https POST to the same URL and it works. It only seems to fail from PRTG. has anyone had similar issues with these or can help me understand the error? I've used http action notifications many times before but never to a URL that isn't within my organisation.


Article Comments

Hi nocDan,

on the information tooltip for the "Cutom URL" control it is mentioned: "Note: Please use the GET method to request the URL. POST requests are not supported."

What I just discovered on search for OpsGenie ( I have no experience with it) is a guideline for the combination with PRTG here: https://docs.opsgenie.com/docs/prtg-integration

Perhaps this will help to get it running. Regards, jo


Apr, 2018 - Permalink

Hi Jo,

The http notification does use POST, I'm not setting up a sensor here. I've also worked with OpsGenie support as they cannot recreate the issue and it works from other sources I'm trying to understand why PRTG is unable to send the POST and gets the SSL error.


Apr, 2018 - Permalink

Just a thought. We are running PRTG as the free version while we perform proof of concept. We'll be moving to a full version before moving into production. If there a limitation on sending notifications via https when the free trial has expired?


May, 2018 - Permalink

Hi!

The free PRTG version has only one limit: 100 sensors.


Kind regards
Andreas Günther, Technical Support


May, 2018 - Permalink

Hello,

Did you ever get this worked out, I've hit the same thing today, sames errors about SSLv3, I've upgraded to the latest versions and still nothing.

any help would be amazing.


Mar, 2019 - Permalink

I have an answer to this: At the bottom of the guide (https://docs.opsgenie.com/docs/prtg-integration) there is this:

Troubleshooting If you are having trouble sending execute actions to OpsGenie, enable Send SNI and add opsgenie.com for US, eu.opsgenie.com for EU.

This was the key for me.


Apr, 2019 - Permalink