I'm trying to configure the Auto-Update feature in PRTG. We have a webproxy which uses Web Proxy Autodiscovery Protocol (WPAD) and authenticates users with Active Directory.
I configured the proxy settings in PRTG but no matter what username I enter or if I leave the username blank I get the error (Error in autoupdate (Socket Error # 10060 Connection timed out..
If I open the proxy logs there is nothing in it, so PRTG did not even try to use the proxy as specified. Seems like it is ignoring the settings. I tried different ways to enter the proxy in PRTG: IP adress, Hostname, FQDN but none of them work.
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Our Enterprise Security Policy does not allow direct internet connections per Se. All connections have to go through a proxy, no execeptions. Can you implement proxy support for the auto-update functionality in a future release of PRTG ?
Dec, 2011 - Permalink
This subject is already up for consideration but an implementation of such a function is not determined for the near future. Please bear with us.
Dec, 2011 - Permalink
These are bare basics. We need proxy support like 99.99999% of all other enterprises probably do too. Please implement.
Mar, 2012 - Permalink
It's on the list, but does not have a high priority, seeing as obviously it's not that highly requested here. Nevertheless, your vote is of course counted.
Mar, 2012 - Permalink
Please add my vote to implement this feature as well. We have 3 PRTG servers running and this feature will be of great benefit for us. We have the same policies within our corporate environement.
Thanks
May, 2012 - Permalink
your vote is counted and we are already working on it, but it will still need a little more time, sorry.
May, 2012 - Permalink
We need proxy support like 99.99999% of all other enterprises probably do too. Please implement.
May, 2012 - Permalink
Hi,
we are working on a "proxy auto-update" feature at the moment. No release date has been determined yet but most likely it will be in Q3/2012.
Best regards
May, 2012 - Permalink
Just wanted to add my vote for this feature also as I too am in an environment where web traffic must go through a proxy.
I presume this issue still applies for product activations too.
May, 2012 - Permalink
Please add my vote to this feature. Our enterprise network policy requires all internet access to be routed via an authenticated proxy server.
Jul, 2012 - Permalink
This should be released in the next weeks, it's already available in the Canary Builds, and should be this week in the Preview builds.
Jul, 2012 - Permalink
July 29th 2012 - Version 12.3.1.2419/2420 [Stable]
New [Core]: Proxy support for various Core Server functions: Auto update, geo map tile proxy, activation, http notifications, SMS text message notifications (set this up in the "System & Website" settings).
Not tested yet but woohoo!
Sep, 2012 - Permalink
While PRTG originally used the proxy configuration for HTTP sensors only, since version 12.3.1 PRTG is able to use the proxy configuration for various functions.
| July 29th 2012 - Version 12.3.1.2419/2420 [Stable] | New [Core]: Proxy support for various Core Server functions: Auto update, geo map tile proxy, activation, http notifications, SMS text message notifications (set this up in the "System & Website" settings). |
For the proxy's set-up, please review:
Core and Probe Settings
Please find also a list of external servers used by PRTG here:
Which servers does PRTG connect to for Software Auto-Update, Activation, etc.?
Best regards,
Sebastian
Sep, 2016 - Permalink
Hello,
the proxy-settings in PRTG only apply for HTTP Sensors. The Auto-Update will not use those settings (like the Activation). These need a direct connection to the internet.
best regards.
Dec, 2011 - Permalink