New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Execute HTTP Action with TLS1.2

Votes:

1

Your Vote:

Up

Down

Hello, we are trying to implement Execute HTTP action feature on notifications, but we're not able to do so.

If we execute call from powershell with invoke-webrequest everything works fine, but from prtg, we're getting errors.

"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 (Sensor/Source/ID: 17409/17409/1)"

We have checked everything that can be checked.

PRTG version we're running is: 18.4.45.1898+.

Any help would be appreciated, since from all other systems integration is working properly. Target web server works only under TLS 1.2, and have a valid certificate since it works from other systems.

execute-http-action prtg ssl-certificate tls

Created on Oct 23, 2018 2:45:08 PM by  nikola30 (1) 1

Last change on Feb 13, 2020 2:13:42 PM by  Luciano Lingnau [Paessler]



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello there,

It should work from PRTG as well with "TLS 1.2 only". Does it work in Powershell when run on the PRTG server as well? Is there maybe a proxy configured in PRTG?

To take a deeper look into this, please run a Wireshark capture on the PRTG server, one time when calling the url from Powershell and then another one when PRTG calls the url. You can also use a capture filter in Wireshark so that it only captures the traffic between PRTG and the target ip to keep the record smaller.

If you need to have as a look at the captures as well, send them to us by email ([email protected]) and mention this thread in your email.

Kind regards,

Erhard

Created on Oct 24, 2018 12:03:43 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi there, i have the exact same problem. The endpoint renewed the certificate and now I have this SSLv3 handshake error.

Created on Mar 28, 2019 1:38:41 PM by  quentinB (0)



Votes:

0

Your Vote:

Up

Down

Hi Quentin,

Please see Erhards post as we need more details to troubleshoot this properly.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Mar 29, 2019 8:00:07 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.