I applied a GoDaddy SSL to our internet facing PRTG server and at the same time changed our probe from connecting via local 127.0.0.1 to remote connecting via the internal IP of our PRTG server.

Since then the Netflow since has reported No data (since 3/31/2011 10:37:41 AM). I installed the Netflow tester on the PRTG server and am seeing netflow traffic arriving over the defined port.

The Netflow sensor is configured to receive on the same internal IP and port it has always been using. What can I do to get this working?

Thanks, Randy

Article Comments

Hello,

there should be no relation between a Certificate for the Webserver of PRTG and the probes. Therefore is there a specific reason why you run the Local Probe now as Remote Probe? Can you change that to run as Local Probe on 127.0.0.1 again?

Best regards.


Apr, 2011 - Permalink

Hi! Changing the probe back to a local probe resolved the problem. When I originally applied the SSL I had issues and changed to a remote probe thinking that would help. I had to redo the OpenSSL request which resolved it. I never changed the probe back to local.

Thanks for the quick response! I am a big PRTG fan!

Any idea when PRTG 9 is gonna be release?

Thanks, Randy


Apr, 2011 - Permalink

We are aiming for Q4 this year for PRTG 9. Please bear with us.


Apr, 2011 - Permalink