Swindle

I have two proxy servers. I had this 'ProxyRemote * hxxp://10.96.2.31:3128' in my original global config, because I thought that statement forwarded to 10.96.2.31, saying it was the ProxyRemote. Instead, I should have added 'ProxyRemote * hxxp://10.32.2.2.3:3128' to the alternate proxy server configuration. The blocking was coming from the Cisco Meraki device at the remote location. I never realized it was trying to hit the remote location, which caused the confusion. I'm good now.

I found the issue. I thought I had to have my proxyremote statement in the global proxy configuration, pointing to the remote proxy chain. It appears it needed to be on the remote proxy pointing to the global proxy. Does that sound accurate? We do have a Cisco Meraki device at the remote site, which was probably blocking.

Hi, I'm troubleshooting an issue with my proxy servers. When they reach out to the ESET servers, they are receiving a 403 forbidden error. The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it. So, this leads me to ask this question. Do the ESET update servers REQUIRE secure connectivity? I haven't seen anything in the documentation that states it requires it. Observing the screenshot, 10.32.14.106 is the client and 10.32.2.23 is my proxy server. Thanks!