01-21-2012 02:50 AM
OK, I tested the access to the URL that you indicated. I accepted the warning about the invalid certificate and -despite of that- gave my OK to enter the page. This is the warning that pop up right after: "The requested URL "/", is invalid. Reference #9.311fed5.1327142789.18ab3010". This was the end of the story, no way to do anything else.
--the certificate should come up as invalid... the product validates the certificate however, and so can you.
Validate the certificate and see if it lets you through. The fact that you got as far as certificate validation tells me that it should... which then raises the question of why autoupdate can't.
There's also the possibility that your filter is filtering the update connection for some reason.
01-23-2012 09:11 AM
OK, so you're able to connect just fine; I think we'll need help from the dev team to take this any further, as it appears your proxy is handling conenctions to the site just fine.
The only other things I can think of is that your SSL connection is failing due to the a similar issue to the one that has been plaguing others on this board... either your timestamp on your proxy is incorrect, or your proxy software is fighting with the Sophos software for exclusive use of the SSL libraries. The latter is being fixed in a new version of SAV HE; the first needs to be fixed on your proxy if it is indeed an issue.
02-04-2013 06:54 AM
I'm experiencing issues when attempting to update my virus definitions.
If I bring the 'Autoupdate window' up, I see an error message: 'Could not contact primary server'.
I am however, also using a firewall. Could you please advise what URL's/ port numbers are required to be allowed within the firewall to allow access to the Sophos autoupdate server?