Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Problem with license synchronization - Synchronization with server failed (Device not found)

I've got a problem with my XG Firewall.
It cannot connect to a license server. I can't use any of the advanced features because of that.
In "tail -f /log/licensing.log" it says that "Device not found", and "Problem with the local SSL certificate".
I recently reseted it to default settings, but it still is not able to contact license server.
I don't know what should I do.



This thread was automatically locked due to age.
Parents Reply Children
  • Hello,

    did we get the solution on this?

    I have open case and waiting for the 3rd for some India support guy to call.

    Previously it was not working because of DNS and Time(maybe).

    Now everything is correct but agai "Device not found".

    But I see it in(serial number) my.sophos.com and when try to register(as it initial setup) it says - already registered.

    Could you please help? Will be highly appreciated!

  • I've seen this before; it was due to the software license serial number being used on more than one installation of XG -- this messes things up (it was accidental in my case).  They had to manually go in and do something on the licensing server(s) to allow things to work again.  It's been a while but this seems similar.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • Software appliance? Likely causing this. 

    Check the /log/licensing.log 

    There is something called "Device-ID". Check old logs and new logs, compare them and check, if the Device ID changed somehow. If so - That is likely causing the Issue. 

    __________________________________________________________________________________________________________________