I have a requirement to install a remote probe behind a proxy server. The server that the Remote Probe is to be installed is able to connect to the PRTG server via the proxy, but the PRTG Remote Probe is unable to get out. Are there any magic Registry settings that can be used to make the remote probe connect via a proxy.
There is no opportunity for this site to have a direct internet connection. It must use the proxy.
Pabs
Article Comments
May i suggest that this is added as a feature moving forward. I have a number of customer sites that I manage solutions for and I would love to be able to deploy PRTG to these sites. I am not able to provide dedicated external connections as this is against customers policies. This is likely to be the case for most organisations that employ a proxy server.
Nov, 2016 - Permalink
We get this request quite often, but we simply don't want to add another point of failure to the connection, given that the troubleshooting of core probe connections is already rather complex :)
Nov, 2016 - Permalink
When you say "You'll have to create an exception...." do you just mean on the firewall?
Apr, 2017 - Permalink
What I meant was to make the probe directly to the internet, without the need of a proxy server.
So the exception would be added within the appliance that blocks the probe from connecting directly.
Apr, 2017 - Permalink
As we know that remote cab is not connected with proxies. I also try with Microleves Dedicated proxies https://microleaves.com/services/dedicated-proxies/ But it works for me how i don't know you should try this. Hope it works fine for you also.
May, 2017 - Permalink
Hi Viswanathan,
I'm afraid that there is no change yet here. The Core - Probe connection is working the same way.
Kind regards
Felix Wiesneth - Team Technical Support
Jun, 2022 - Permalink
Sorry, remote probes cannot connect via proxy. You'll have to create an exception or connect the probe directly to the internet, no way around that.
Nov, 2016 - Permalink