This article applies to PRTG Network Monitor 14 through 17.3.33
SSL secure channel error with HTTP sensors
Note: The content of this article only refers to the deprecated HTTP SSL Certificate Expiry sensor.
If you use the deprecated HTTP SSL Certificate Expiry sensor, you have the option to force an SSLv3 connection in the sensor settings. However, the monitored URL might only accept ciphers for SSL connections that will allow for Perfect Forward Secrecy. This enhances connection security.
The Force usage of SSLv3 option in the SSL Connection settings of this sensor type is not capable of these strong ciphers. If you selected to force SSLv3 for connections and the defined HTTPS URL uses forward secrecy, the sensor will show the error Could not create SSL/TLS secure channel because of this.
Moreover, the PRTG server only accepts SSL connections with forward secrecy as of version 14.4.12, so you will also get this error if you monitor your PRTG certificate using the Force usage of SSLv3 option.
To avoid this SSL error, you have to select the option Use SSLv3 if available. Actually, this option is even more secure than forcing SSLv3 because it will automatically use the most secure connection. This is why connections to URLs with forward secrecy will only work if you select this setting.
Click to enlarge.
Note: The error message Could not create SSL/TLS secure channel also appears if you request an SSL-secured URL via HTTP.
Note: error message depends on your Windows language
Error messages of sensors that use the Microsoft .NET Framework such as the HTTP sensors mentioned above come directly from .NET. Because of this, the language of these messages depend on your Windows version. Below you can find the Could not create SSL/TLS secure channel message in other languages:
- Es konnte kein geschützter SSL/TLS-Kanal erstellt werden.
- No se puede crear un canal seguro SSL/TLS
- Impossible de créer un canal sécurisé SSL/TLS
- Não foi possível criar um canal seguro para SSL/TLS
- Kan geen beveiligd SSL/TLS-kanaal maken
- Impossibile creare un canale sicuro SSL/TLS.
Add comment