Aabed

we're planning to upgrade clients to v6 eventually, but this will happen gradually. our main concern right now is updates as all clients have been outdated for over a week! for now, i've managed to apply policies for all clients, i just figured out that the server's version "File Security" applies only the policy File Security for Windows Server - HTTP Proxy Usage, after pushing this policy those clients were configured correctly (update server set to automatic and proxy set to Apache Cache) but none was updating with the error user and password not set, i added the user and password in the policy and updates were flowing. my question is does setting the user and password still updates through cache server? how can i be certain that clients are updating from cache server and not ESET? i'd really like to confirm this as it would create an enormous traffic if updating from ESET, causing a major network issue. hopefully this would be our last issue with the updates!

Hello Marin, i activated the clients from ERA successfully, those clients seemed to be having a conflict in their policy, i removed all policies leaving two with the below settings: UPDATE: update server: autoselect proxy server: Apache proxy no user\pwd required TOOLS: proxy server: Apache proxy no user\pwd required however, for the troublesome users, when request their configuration from ERA i find there's a password set for the apache proxy with no username, even though it's not configured in the policy (p.s. i triple checked, there's no additional policies applied) this update issue is driving me nuts! have a look at this server in the below logs, it has the same policies and i couldnt update it as well, when i activated it through ERA it registered the EAV-username and password in its client automatically but i dont think its updating via proxy, any idea what's going on?? proxy_log.txt

i tried updating locally (from eav) for clients that were failing to update through pushing update from ERA. when i click update from their EAV, it prompts for a user name and password! my proxy server has no user name/password set! any idea what this could be?

hi Marcos, thank you for your reply. i did set the proxy to ERA's Apache server and set the update server to AUTOSELECT, i tried updating my clients then, 2/5 did update! so you're right about this, i'm wondering why only 2 updated. just one thing though, you said Proxy under Tools, which i did, but what about proxy server under Updates? i have this one set to Apache proxy. additionally, how would i know that clients are updating from Apache's cache or updates.eset.com, i need to verify this before going forward deploying agents. thanks for your help, appreciate it!

hello everyone, i'll make this short, we upgraded ERA 5.x to 6.x recently, i know there have been too many frustration over the new ERA but i managed to get my way through looking around the forums for similar issues. my bumper right now is obviously the updates which is a huge concern (over 340 clients with outdated DB). here's what was done: Apache HTTP proxy was installed with the all-in-one installer Apache HTTP proxy was configured as per the article here did not set a password for Apache access webpage access test for Apache installation (hxxp://localhost:3128/index.html) is accessible successfully policy was made to set update server as per the same article above clients being tested have agent installed clients being tested are using EAV v 5.x in the EAV client: when i enter the update server as 200.200.200.25:3128 > apply > try updating. i get bad link to update server p.s.: 200.200.200.25 is ERA's server i checked the Apache error log and found this not so helpful log: AH01797: client denied by server configuration: proxy:hxxp://200.200.200.25:3128/update.ver i double checked the httpd.conf file just to make sure i applied the configuration as illustrated in the article, while doing so, i did set the logging to debug and under <Proxy *> i changed deny from all to allow from all restarted Apache service tried update on client again, it failed again i checked Apache error log again and got the below logs: most notably the File does not exist: C:/Program Files/Apache HTTP Proxy/htdocs/update.ver mod_cache.c(717): (OS 5)Access is denied. : [client 200.200.200.180:63461] AH00765: cache: Cache provider's store_body failed for URI hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup appreciate your help guys here's some of the last line in the log file: [Thu Nov 26 13:59:10.813126 2015] [authz_core:debug] [pid 4728:tid 1332] mod_authz_core.c(834): [client 200.200.200.180:63461] AH01628: authorization result: granted (no directives) [Thu Nov 26 13:59:10.813126 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(505): [client 200.200.200.180:63461] AH00757: Adding CACHE_SAVE filter for hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:10.813126 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(539): [client 200.200.200.180:63461] AH00759: Adding CACHE_REMOVE_URL filter for hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:10.813126 2015] [proxy:debug] [pid 4728:tid 1332] mod_proxy.c(1157): [client 200.200.200.180:63461] AH01143: Running scheme http handler (attempt 0) [Thu Nov 26 13:59:10.813126 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2145): AH00942: HTTP: has acquired connection for (*) [Thu Nov 26 13:59:10.813126 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2199): [client 200.200.200.180:63461] AH00944: connecting hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nupto update.eset.com:80 [Thu Nov 26 13:59:10.828751 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2408): [client 200.200.200.180:63461] AH00947: connected /v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup to update.eset.com:80 [Thu Nov 26 13:59:10.875626 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2782): AH02824: HTTP: connection established with 38.90.226.39:80 (*) [Thu Nov 26 13:59:10.875626 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2936): AH00962: HTTP: connection complete to 38.90.226.39:80 (update.eset.com) [Thu Nov 26 13:59:12.219376 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2160): AH00943: *: has released connection for (*) [Thu Nov 26 13:59:12.219376 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2878): [remote 38.90.226.39:80] AH02642: proxy: connection shutdown [Thu Nov 26 13:59:12.219376 2015] [cache:debug] [pid 4728:tid 1332] cache_storage.c(664): [client 200.200.200.180:63461] AH00698: cache: Key for entity hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup?(null)is hxxp://update.eset.com:80hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup? [Thu Nov 26 13:59:12.219376 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(1333): [client 200.200.200.180:63461] AH00769: cache: Caching url: hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:12.219376 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(1339): [client 200.200.200.180:63461] AH00770: cache: Removing CACHE_REMOVE_URL filter. [Thu Nov 26 13:59:12.219376 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(717): (OS 5)Access is denied. : [client 200.200.200.180:63461] AH00765: cache: Cache provider's store_body failed for URI hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:12.250626 2015] [authz_core:debug] [pid 4728:tid 1332] mod_authz_core.c(834): [client 200.200.200.180:63471] AH01628: authorization result: granted (no directives) [Thu Nov 26 13:59:12.250626 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(505): [client 200.200.200.180:63471] AH00757: Adding CACHE_SAVE filter for hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:12.250626 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(539): [client 200.200.200.180:63471] AH00759: Adding CACHE_REMOVE_URL filter for hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:12.250626 2015] [proxy:debug] [pid 4728:tid 1332] mod_proxy.c(1157): [client 200.200.200.180:63471] AH01143: Running scheme http handler (attempt 0) [Thu Nov 26 13:59:12.250626 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2145): AH00942: HTTP: has acquired connection for (*) [Thu Nov 26 13:59:12.250626 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2199): [client 200.200.200.180:63471] AH00944: connecting hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nupto update.eset.com:80 [Thu Nov 26 13:59:12.250626 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2408): [client 200.200.200.180:63471] AH00947: connected /v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup to update.eset.com:80 [Thu Nov 26 13:59:12.391251 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2782): AH02824: HTTP: connection established with 38.90.226.39:80 (*) [Thu Nov 26 13:59:12.391251 2015] [proxy:debug] [pid 4728:tid 1332] proxy_util.c(2936): AH00962: HTTP: connection complete to 38.90.226.39:80 (update.eset.com) [Thu Nov 26 13:59:12.610001 2015] [cache:debug] [pid 4728:tid 1332] cache_storage.c(664): [client 200.200.200.180:63471] AH00698: cache: Key for entity hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup?(null)is hxxp://update.eset.com:80hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup? [Thu Nov 26 13:59:12.610001 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(1333): [client 200.200.200.180:63471] AH00769: cache: Caching url: hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:12.610001 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(1339): [client 200.200.200.180:63471] AH00770: cache: Removing CACHE_REMOVE_URL filter. [Thu Nov 26 13:59:12.610001 2015] [cache:debug] [pid 4728:tid 1332] mod_cache.c(717): (OS 5)Access is denied. : [client 200.200.200.180:63471] AH00765: cache: Cache provider's store_body failed for URI hxxp://update.eset.com/v5-rel-sta/mod_023_pegasus_7229/em023_32_l0.nup [Thu Nov 26 13:59:39.797501 2015] [authz_core:debug] [pid 4728:tid 1340] mod_authz_core.c(834): [client 192.168.50.44:54297] AH01628: authorization result: granted (no directives) [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] mod_proxy.c(1157): [client 192.168.50.44:54297] AH01143: Running scheme http handler (attempt 0) [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2145): AH00942: HTTP: has acquired connection for (*) [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2199): [client 192.168.50.44:54297] AH00944: connecting hxxp://200.200.200.25:3128/update.verto 200.200.200.25:3128 [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2408): [client 192.168.50.44:54297] AH00947: connected /update.ver to 200.200.200.25:3128 [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2782): AH02824: HTTP: connection established with 200.200.200.25:3128 (*) [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2936): AH00962: HTTP: connection complete to 200.200.200.25:3128 (200.200.200.25) [Thu Nov 26 13:59:39.797501 2015] [authz_core:debug] [pid 4728:tid 1348] mod_authz_core.c(806): [client 200.200.200.25:2722] AH01626: authorization result of Require all granted: granted [Thu Nov 26 13:59:39.797501 2015] [authz_core:debug] [pid 4728:tid 1348] mod_authz_core.c(806): [client 200.200.200.25:2722] AH01626: authorization result of <RequireAny>: granted [Thu Nov 26 13:59:39.797501 2015] [core:info] [pid 4728:tid 1348] [client 200.200.200.25:2722] AH00128: File does not exist: C:/Program Files/Apache HTTP Proxy/htdocs/update.ver [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2160): AH00943: *: has released connection for (*) [Thu Nov 26 13:59:39.797501 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2878): [remote 200.200.200.25:3128] AH02642: proxy: connection shutdown [Thu Nov 26 14:00:19.063126 2015] [authz_core:debug] [pid 4728:tid 1340] mod_authz_core.c(834): [client 192.168.50.46:52218] AH01628: authorization result: granted (no directives) [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] mod_proxy.c(1157): [client 192.168.50.46:52218] AH01143: Running scheme http handler (attempt 0) [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2145): AH00942: HTTP: has acquired connection for (*) [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2199): [client 192.168.50.46:52218] AH00944: connecting hxxp://200.200.200.25:3128/update.verto 200.200.200.25:3128 [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2408): [client 192.168.50.46:52218] AH00947: connected /update.ver to 200.200.200.25:3128 [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2782): AH02824: HTTP: connection established with 200.200.200.25:3128 (*) [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2936): AH00962: HTTP: connection complete to 200.200.200.25:3128 (200.200.200.25) [Thu Nov 26 14:00:19.063126 2015] [authz_core:debug] [pid 4728:tid 1348] mod_authz_core.c(806): [client 200.200.200.25:2736] AH01626: authorization result of Require all granted: granted [Thu Nov 26 14:00:19.063126 2015] [authz_core:debug] [pid 4728:tid 1348] mod_authz_core.c(806): [client 200.200.200.25:2736] AH01626: authorization result of <RequireAny>: granted [Thu Nov 26 14:00:19.063126 2015] [core:info] [pid 4728:tid 1348] [client 200.200.200.25:2736] AH00128: File does not exist: C:/Program Files/Apache HTTP Proxy/htdocs/update.ver [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2160): AH00943: *: has released connection for (*) [Thu Nov 26 14:00:19.063126 2015] [proxy:debug] [pid 4728:tid 1340] proxy_util.c(2878): [remote 200.200.200.25:3128] AH02642: proxy: connection shutdown