Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unable to check for update netgate sg-2220 release 21.05

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    5 Posts 4 Posters 799 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mrbabiebob
      last edited by

      On a Netgate SG-2220 Release 21.05 I am unable to update packages or check for system updates.

      I did follow the update debug steps, they dont work for this issue.

      I did shutdown, completely removed power + boot up. See the cert validation failure here and the Authentication error

      pkg update -f
      Updating pfSense-core repository catalogue...
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA
      34376073216:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2105-amd64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
      pkg: https://files00.netgate.com/pkg/pfSense_plus-v21_05_amd64-core/meta.txz: Authentication error
      repository pfSense-core has no meta file, using default settings
      
      
      1 Reply Last reply Reply Quote 0
      • M
        mrbabiebob
        last edited by

        Okay the system time/date was totally wrong. :|

        I was able to spot it with openssl s_client -connect files01.netgate.com:443 which gave me verify error:num=9:certificate is not yet valid.

        Indeed the system date/time was set in 2017.

        Looks like it's caused by dns resolution not working hence ntpd failing to sync time since update :(

        R 1 Reply Last reply Reply Quote 0
        • R
          ridek724 @mrbabiebob
          last edited by

          @mrbabiebob said in Unable to check for update netgate sg-2220 release 21.05:

          Okay the system time/date was totally wrong. :|

          I was able to spot it usps tracking with openssl s_client -connect files01.netgate.com:443 which gave me verify error:num=9:certificate is not yet valid.

          Indeed the system date/time was set in 2017.

          Looks like it's caused by dns resolution not working hence ntpd failing to sync time since update :(

          Even i have noticed that there is no updates
          Thanks & Regards
          redik

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @ridek724
            last edited by

            @ridek724 Did you find Upgrade not Offered / Library Errors

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              The SG-2220 does not have an RTC clock battery so if it's been off for some time it may revert to the initial time/date.
              If you do not have at least one NTP server defined by IP and you have DNSSec enabled in Unbound and no other DNS servers set then you have a chicken/egg situation. The firewall cannot recolve any time servers because DNS doesn't work when the clock is wrong!

              Setting either a fixed NTP server or an alternative DNS server will prevent that.

              Steve

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.