I am trying to configure a "HTTP Push Data Advanced" sensor with TLS on a device managed by a remote probe.
When starting the sensor, I get the following error:
PRTG could not start the HTTP push receiver. Could not load root certificate. error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib (code: PE206) "Could not load root certificate".
As I have not configured any custom certificate, I was under the impression that PRTG should use its embedded certificate. I tested with a similar sensor on a local probe, and it works as expected.
Is there a way to configure the remote probe so it works?
Article Comments
I have several certificates on windows store, but none that would be explicitely be a prtg one. (I did not change the certificate self-signed shipped with prtg).
When you say "restart the device" you mean restart the host where the remote probe runs?
Oct, 2020 - Permalink
Yes, I mean the server where the Probe runs. In this way, a new sync with the Core server is triggered which could solve the issue.
Oct, 2020 - Permalink
I have tried to
- restart the probe service
- restart the server hosting the probe
It does not help, it seems that ssl server on port 5051 fails to start on the probe (telnet localhost 5051 never works).
The error message still is
PRTG could not start the HTTP push receiver. Could not load root certificate. error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib (code: PE206)
Not sure if it helps but I have only dh, dh.pen, openssl.cnf and generatedh files in c:\program files (x86)\prtg network monitor\cert. I have try looking at the probe logs, but nothing seems to point to any problem.
Oct, 2020 - Permalink
Thank you for the feedback. Please try to use the REST Custom Sensor, since this Sensor is quite similar and we noticed that this Sensor works if the HTTP Advanced Sensor has trouble.
Oct, 2020 - Permalink
Sorry, but unless I am wrong the "REST Custom" permits to query an HTTP(s) ressource, not receiving sensor data from another source. I am using 20.3.61.1649+ maybe you are talking about another sensor not present in my version.
What I need is the PRTG probe to open an SSL http port on 5051 so I can push json data to update data (I am talking about "HTTP Push Data Advanced" Sensor).
Oct, 2020 - Permalink
I'm sorry I missed that. Please let me know whether you checked if the port is already take via "netstat -ano" ? In addition, did you tried to open another port since you can change the port in the Sensor settings?
Oct, 2020 - Permalink
Port is available. I just tried on another port (5055) and the error is still the same.
Oct, 2020 - Permalink
Since troubleshooting in the knowledge base is not the best way, please open a support ticket with all available information. You can simply write an email to "support@paessler.com". Please mention my name so the ticket is assigned to me.
Thank you!
Oct, 2020 - Permalink
Hi, we have the same issue on Push count sensors. Is there any progress on this issue? Do I need to open a case also? Thanks.
Jun, 2021 - Permalink
Hi there,
At the moment, we have no known issue in the latest PRTG version which could explain the issue. Therefore, please create a ticket so that we can analyse the issue in more detail.
Jun, 2021 - Permalink
Hi,
just for the sake of completeness IMHO this error can be solved by copying following files from core server to remote probe and restarting remote probe service.
C:\Program Files (x86)\PRTG Network Monitor\cert\prtg.crt
C:\Program Files (x86)\PRTG Network Monitor\cert\prtg.key
C:\Program Files (x86)\PRTG Network Monitor\cert\root.pem
Sep, 2022 - Permalink
Please check the certificate store on the Windows Server where the Probe runs whether there is a certificate stored. In addition, did you tried to restart the device?
Oct, 2020 - Permalink