This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Could not contact Primary Server

Got this message when updating Sophos Home Edition for Mac:

Could not contact Primary Server. URL Error: 3 July 2015

Mac OS X 10.10.4

Sophos Home Edition 9.2.4

As I'm in Australia and this is first report for 3rd July, am thinking this may be a cloud error with Sophos infrastructure.

If not, there's something else amiss... have cleared cache and restarted.

:1021170


This thread was automatically locked due to age.
  • Hey ACR

    I just merged your post with this thread so we can make the issue easier to track. Please, if you could take a look at my previous post, and provide the requested troubleshooting information, that would be really helpful. If you have any questions just let me know. 

    :1021271
  • Hey everyone,

    Just wanted to let you know we're looking into this issue and do appreciate your patience. One additional peice of data I've been asked to gather is a TCP capture. This can be somewhat complicated for the average user, but I'll try my best to explain step by step. 

    1. Spotlight search "terminal" and press enter.

    2. Copy and paste this command and press enter: ifconfig

    • make note of the 'active' interface name
    • in the example below, the active interface is en0
    • you will need to know the active interface for the next step


    Note: It's best to do the next steps as quickly as possible, otherwise the tcpcapture will genrate an extremely large file, which could cause issues when attempting to email the file. I would recommend reading through all the steps before you proceed. 

    4. Copy and paste the below command into the terminal. Replace <interface> with the number from step 1. For example, mine would look like this:  sudo tcpdump -w capture.pcap -s 0 -i en0 port 80

    sudo tcpdump -w capture.pcap -s 0 -i <interface> port 80

    5. When you are ready to start, hit enter

      • If prompted for a password, enter your admin password (same as you use to install software on your mac)

    6. Click the Sophos sheild icon and click on Update Now

    7. As soon as the update fails, go back to your terminal window and hit control-c or command-c to quit the capture

    8. This will create a file on your hard drive called capture.pcap. Spotlight search for this file and email it to me > serra@sophos.com

    Whew! I know it's a lot of work, good luck and let me know if you have questions. 

    :1021288
  • Thanks for your help Serra,

    Problem solved now for me.  Hope you've been successful solving it for everyone!

    :1021289
  • having the same issues here and trying out your troubleshooting - just wondering which 'active' line i need - en0 or en1? en2 is 'inactive'........

    thanks :)

    :1021291
  • Auto Update not working since 2 weeks.

    Info requested (I edited few entries for privacy purposes)

    1)

    traceroute -I dci.sophosupd.com

    traceroute to sophos-1.hs.llnwd.net (178.79.212.154), 64 hops max, 72 byte packets
    1 to 5 entries removed for privacy purposes
     

     6  tge8-3.fr4.sin.llnw.net (117.121.248.44)  49.868 ms  56.409 ms  49.976 ms

     7  ve5.fr3.sin.llnw.net (117.121.248.1)  50.956 ms  58.080 ms  50.870 ms

     8  tge7-4.fr3.tyo.llnw.net (117.121.255.214)  126.920 ms  197.940 ms  199.956 ms

     9  ve5.fr4.tyo.llnw.net (203.77.184.206)  164.428 ms  129.742 ms  139.271 ms

    10  ve7.fr3.tyo3.llnw.net (203.77.184.234)  142.593 ms  127.949 ms  127.680 ms

    11  tge11-4.fr3.sjc.llnw.net (203.77.184.245)  251.884 ms  307.296 ms  244.966 ms

    12  ve5.fr4.sjc.llnw.net (69.28.171.210)  242.781 ms  309.371 ms  251.417 ms

    13  tge9-4.fr4.ord.llnw.net (69.28.172.78)  363.065 ms  451.273 ms  268.269 ms

    14  tge5-6.fr4.lga.llnw.net (69.28.172.197)  347.654 ms  271.783 ms  342.377 ms

    15  tge13-4.fr4.ams.llnw.net (69.28.189.50)  307.271 ms  281.647 ms  332.596 ms

    16  tge14-5.fr4.arn1.llnw.net (87.248.220.157)  307.678 ms  314.840 ms  307.484 ms

    17  https-178-79-212-154.arn1.llnw.net (178.79.212.154)  307.678 ms  611.779 ms  616.653 ms

    2)

    ping -c 5 dci.sophosupd.com
    PING sophos-1.hs.llnwd.net (178.79.212.154): 56 data bytes
    64 bytes from 178.79.212.154: icmp_seq=0 ttl=53 time=307.718 ms
    64 bytes from 178.79.212.154: icmp_seq=1 ttl=53 time=307.756 ms
    64 bytes from 178.79.212.154: icmp_seq=2 ttl=53 time=307.671 ms
    64 bytes from 178.79.212.154: icmp_seq=3 ttl=53 time=310.309 ms
    64 bytes from 178.79.212.154: icmp_seq=4 ttl=53 time=348.161 ms

    I have emailed you the wireshark captures

    :1021299
  • Hey everyone,

    Over the weekend I recieved a few packet captures from you, which I have forwarded over to our Operations team. Currently, we have a ticket open with our CDN provider, who is investigating this issue. 

    I'm sorry I still don't have a full resolution just yet, but all the troubleshooting data you've provided has been really helpful in moving our case forward, so I wanted to say thanks for all your help and patience while we continue to troubleshoot this issue.

    :1021306
  • Hey Gnitch,

    If you copy / paste the output of the 'ifconfig' command into your reply I can answer that for you. :cathappy:

    :1021307
  • Hi everyone,

    Ok, we just made some changes which we believe may have corrected this issue.

    Can you please retest and let me know if you're still unable to update?

    Cheers,

    :1021313
  • Thank you very much, Serra and Sophos.

    My anti-virus updated successfully.

    Theo-P

    :1021322
  • Mine also updated OK. Thanks to you and everyone who helped.

    :1021323