Relay and Cache Server could not update because wrong proxy

Question

Hello @all, 
 our win 2016 Server with installed relay and cache server are using a wrong proxy configuration: 
 Trying update service URL sus.sophosupd.com/.../dae1076b-8473-4c45-8c3a-076246744ca6 with proxy: 87.xx.xx.94:443 
 On Central, I have changed the proxy and disable that, but our server are still using the wrong proxy. 
 Where can we change that? 
 Many thanks in advance! 
 TBC

Sophos User695 · Accepted Answer

Hello Christian, thank you for your comments. That sometimes the IP and sometimes the FQDN is in it, is due to the call with the corresponding parameter --messagerelay=. I have now found the error thanks to your explanations. The Installation took place without proxy with the Call: *.exe --messagerelays=IP/FQDN, somehow I have always overlooked that this should be so: *.exe --messagerelays=IP/FQDN:8190. Now it seems to work. I have deleted all proxy settings and had forgotten to enter the URL for Central: Zuzulassende Dom&auml;nen und Ports Now everything seems to go so slowly, I watch again because a server still refuses :-) Many thanks to you both Christian and Qoosh!

Qoosh · Answer

No problem at all. All of the Sophos Logs you see where the timestamp ends in "Z" will be in the UTC format. 
 If the service restart did not work, and you've verified the proxy settings in Sophos Central are correct, I suggest trying to remove and re-add the Message Relay and Update Cache component on the affected device. This can be done from the " Manage Update Caches and Message Relays " page. 
 You will want to wait some time after you remove the feature until Sophos Central shows that it has been fully removed. You can then re-add it back. If the issue remains, I suggest opening a support case with our team so they can take a closer look. 
 You can find steps on how to open a case via the Support Portal in the link below. - Create a Technical support case

Relay and Cache Server could not update because wrong proxy

Top Replies