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

UTM 9 Firmware 9.406-3 "Last check" never.

UTM 9 version information is show Last Check "never".  What does this mean?  How do I fix this?



This thread was automatically locked due to age.
Parents
  • Please insert pictures of the three tabs in 'Management >> Up2Date'.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Please insert pictures of the three tabs in 'Management >> Up2Date'.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • Bob,

    I restored the backup to 9.405-5 and that fixed it but after a few update checks,  it stopped updating again. 

    the log;

    Could not connect to Authentication Server us1.utmu2d.sophos.com (code=500 500 Can't connect to us1.utmu2d.sophos.com:443).

    Could not connect to Authentication Server sg1.utmu2d.sophos.com (code=500 500 Can't connect to sg1.utmu2d.sophos.com:443).

  • The configuration backups made on the UTM are marked with the version because you can't restore a version 9.47 backup to firmware version 9.405.  You restored a backup made when your UTM was at firmware level 9.405.

    The error in your log is interesting, and the inability to reach that server is your issue.  Let's first make sure there's not a firewall rule blocking that (unlikely).  Go to the UTM command line and try to ping sg1.utmu2d.sophos.com and then start the Firewall Live Log.

    If the ping executes and there are no blocks in the Live Log, then it's a problem with that server.  In that case, as root at the command line:

    audld.plx --server v8up2date2.astaro.com:443

    What was the result of those commands?  Does the "Never" still appear?  Confirm that the log doesn't show the code=500 error.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • I am getting access denied when trying to login on ssh Putty.  I turned on Shell Access and created a ps.

     

    I figured it out what cause the Up2date issue.  I didn't have a network device in "Network Services" " DNS" "Global" tab list.

    is it normal that sometimes it fail to connect?

    2016:10:12-08:10:17 Could not connect to Server us1.utmu2d.sophos.com (status=500 Internal Server Error).

    2016:10:12-08:10:36 id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"

     

    Thanks again.

  • If you haven't created an RSA key with puttygen and configured key access in WebAdmin, then you will need to login first as loginuser and then su - to login as root.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA