We are running PRTG 17.3.32.2478 and we are using the API to access the sensor date from one of our web servers to provide a filtered view for each customer's systems on our website. The web server wants to connect using TLS 1.2 by default, but PRTG doesn't allow that. We had to force TLS 1.0 on our web server in order to get a successful connection. I found this article (https://helpdesk.paessler.com/en/support/solutions/articles/61769-what-are-the-ssl-changes-in-v-14-4-12-and-how-does-that-affect-me) but the behavior described in the article does not fit with the real world. Am I missing something?


Article Comments

Hello Daniel,

Thank you very much for your contact.

Unfortunately, I am currently not fully understand your request. What do you monitor precisely and how to intend to realize this?

Best regards,
Sebastian


Dec, 2017 - Permalink