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

Sophos XG Firewall Activation Issue "Operation Failed due to an unknown error. Please Contact Support"

FormerMember
FormerMember

Hey Everyone,

I installed Sophos XG Firewall (Home / Personal Use) and ran into issues activating the firewall. When I try to activate it shows a generic error.  "Operation Failed due to an unknown error. Please Contact Support". What additional step am I missing that's keeping me completing the activation?

Note: The WAN port is connected and I'm able to surf the web with no problems. 



This thread was automatically locked due to age.
Parents Reply
  • Hi guys,

    you are all running Sophos XG, there is no difference in the software.

    What you are trying to do is activate your licence which is a different process for home users compared to commercial users.

    You haven't by accident tried to install a commercial licence.

     

    Next trick is a fresh install and see if you can get the trial licence function to work.

    Ian

Children
  • FormerMember
    0 FormerMember in reply to rfcat_vk

    Hi Ian,

    I appreciate the input. I signed up to use the XG home edition using URL  https://secure2.sophos.com/en-us/products/free-tools/sophos-xg-firewall-home-edition/software.aspx. Once I completed the registration process, Sophos sent me an email with the Home Use serial number. I tried activating the serial number through the GUI and through AA option and I receive an error "Operation Failed due to an unknown error. Please Contact Support". 

    I tried using the default ISP DNS and tried statically assigned Google DNS 8.8.8.8 and 8.8.4.4. 

    When I connect my laptop to Sophos XG's LAN port I'm able to surf the web perfectly fine. 

    I'm able to run ping and traceroutes using the Sophos XG command line. 

    I downloaded a newer build of Sophos XG (SW-SFOS_16.05.7_MR-7-305). 

    I'm going to reinstall to see what happens. 

    Thanks. 

  • FormerMember
    0 FormerMember in reply to FormerMember

    I installed the latest version of Sophos XG SW-SFOS_16.05.7_MR-7-305 and still having the same activation issue. Could it be hardware related?

    Motherboard - Asrock Q1900 ITX

    CPU - Intel® Quad-Core Processor J1900 (2 GHz)

    RAM - 8GB of Ram (I understand there will be a limit to how much ram home license will use)

    NIC - HP NC364T PCIe 4 Port Gigabit Server Adapter

    Thanks. 

     

  • Hi,

    I doubt there is an issue with the hardware otherwise you would not have been able to install the software.

    You have previously indicated you could configure the interfaces via CLI.What size disk are you using?

    Ian

  • FormerMember
    0 FormerMember in reply to rfcat_vk

    Hi, 

    I installed the software on a 250GB 7200RPM Seagate drive. 

  • Hi,

    not sure but maybe, your email address you used to sign into the mysophos is different to the one you registered with?

    Grasping at straws here.

     

    ian

  • FormerMember
    0 FormerMember in reply to rfcat_vk

    Hi, 

    I sign in to this forum as well as my Sophos https://secure2.sophos.com/en-us/mysophos/my-account/network-protection/view-devices.aspx with the same email address. I appreciate you taking the time to help me figure this out. 

    Thank you. 

  • FormerMember
    0 FormerMember in reply to FormerMember

    I got around to reinstalling Sophos and noticed a huge improvement in the initial configuration flow. I took my sophos box to my buddies house to see if that would make a difference but that didn't work either. When trying to register my serial number I get the error message"Failed to connect to the registration service" and it shows No Internet Connection. When my laptop is connected to the Sophos LAN port I'm able to surf the web without any issues. When I skip registration and use the ping utility available in the Sophos GUI it works perfectly fine. I successfully pinged various websites and Sophos registration address.  

    Anybody have any ideas what might be causing this issue? Possibly bad NIC?

    Thanks. 

  • Hi,

    sorry, no ideas, but I think there is another thread in the beta forum on the subject.

    Ian