Navigation

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

    Pfsense 2.6 to plus. Unable to check

    Installation and Upgrades
    5
    23
    276
    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.
    • A
      Antibiotic last edited by

      Please fix this issue as I'm check on forum it happened sometimes. Did install fresh copy of pfsense 2.6 and unlucky now))) , to upgrade. Error:Could not load client certificate /etc/ssl/pfSense-repo-custom.cert
      pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Authentication error
      repository pfSense-core has no meta file, using default settings

      1 Reply Last reply Reply Quote 1
      • M
        Michael.Schmalzl last edited by

        Hello,

        have the same Problem.

        I migrated my current APU2's into 23.01 without Problems for the last days and also Installed on my i226 based Machine 2.7 Developer Branch and upgraded to 23.01 until u skrewed up my installation by using the Config from the APU and i had to reinstall until i found out whats happend and skrewd it again :(
        Last install update was showed up but then gone.
        But i finaly got my new machine running with the 2.7 Developer Branch and waiting the problem got fixed.
        As i figured out this Problem happend many times in the last Months and years.

        1 Reply Last reply Reply Quote 0
        • A
          Antibiotic last edited by

          Magic become))) Upgrade done!

          M 1 Reply Last reply Reply Quote 0
          • M
            Michael.Schmalzl @Antibiotic last edited by

            @antibiotic Same on here.
            Woke up, checked it on my tablet and run the upgrade and installed all the things I needed.
            But the root cause would be interesting.

            1 Reply Last reply Reply Quote 0
            • A
              Antibiotic last edited by

              The most funny things that now after success upgrade from CE to 23.01 again mistake:
              pdating pfSense-core repository catalogue...
              pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
              repository pfSense-core has no meta file, using default settings. Please fix this!

              1 Reply Last reply Reply Quote 0
              • A
                Antibiotic last edited by

                My list of available packages are empty now. Can not install any soft))))

                1 Reply Last reply Reply Quote 0
                • A
                  Antibiotic last edited by

                  Error going :
                  Error updating repositories!
                  ERROR: It was not possible to determine pfSense-upgrade remote version

                  1 Reply Last reply Reply Quote 0
                  • A
                    Antibiotic last edited by

                    Next error :
                    A pre-built version of pkg could not be found for your system.
                    Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'

                    1 Reply Last reply Reply Quote 0
                    • A
                      Antibiotic last edited by

                      Have no idea, what is going on!

                      1 Reply Last reply Reply Quote 0
                      • A
                        Antibiotic last edited by Antibiotic

                        Could be to assist for someone. Did fresh renew of Pfsense webConfigurator certificate in strict security mode and after reboot magic happened)))Packages become available)))

                        1 Reply Last reply Reply Quote 0
                        • B
                          barnops last edited by

                          @antibiotic said in Pfsense 2.6 to plus. Unable to check:

                          Please fix this issue as I'm check on forum it happened sometimes. Did install fresh copy of pfsense 2.6 and unlucky now))) , to upgrade. Error:Could not load client certificate /etc/ssl/pfSense-repo-custom.cert
                          pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Authentication error
                          repository pfSense-core has no meta file, using default settings

                          Same.

                          1 week ago I upgraded a firewall from 2.6 to Plus, then to 23.01.

                          Today I went to upgrade a 2nd firewall and am encountering this issue...so it cropped up sometime in the last 7 days.
                          I first factory reset and attempted the update prior to restoring my backup.

                          First "Could not load client certificate...."
                          I remedied this by copying the cert and KEY from the working firewall.

                          Now I am presented with:
                          Updating pfSense-core repository catalogue...
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
                          repository pfSense-core has no meta file, using default settings
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Bad Request
                          Unable to update repository pfSense-core
                          Updating pfSense repository catalogue...
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//meta.txz: Bad Request
                          repository pfSense has no meta file, using default settings
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//packagesite.pkg: Bad Request
                          pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//packagesite.txz: Bad Request
                          Unable to update repository pfSense
                          Error updating repositories!

                          If I run "pkg bootstrap -f" I get this back:

                          The package management tool is not yet installed on your system.
                          Do you want to fetch and install it now? [y/N]: y
                          Bootstrapping pkg from pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/, please wait...
                          pkg: Error fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01//Latest/pkg.txz: Bad Request
                          A pre-built version of pkg could not be found for your system.
                          Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

                          I can't update to Plus, and therefore can't upgrade to 23.01.....very annoying.

                          R 1 Reply Last reply Reply Quote 0
                          • R
                            rcoleman-netgate Netgate Administrator @barnops last edited by

                            @barnops what do you get when you do

                            pfSense-upgrade -c 
                            

                            --
                            Ryan
                            Repeat (after me): MESH IS THE DEVIL! MESH IS THE DEVIL!
                            Requesting firmware for your Netgate device? https://go.netgate.com
                            Switching: Mikrotik, Netgear, Extreme
                            Wireless: Aruba, Ubiquiti

                            B 1 Reply Last reply Reply Quote 0
                            • B
                              barnops @rcoleman-netgate last edited by

                              @rcoleman-netgate said in Pfsense 2.6 to plus. Unable to check:

                              @barnops what do you get when you do

                              pfSense-upgrade -c 
                              

                              When set to the pfSense Plus Upgrade branch:
                              >>> Updating repositories metadata... failed.
                              ERROR: Unable to compare version of pfSense-repo

                              When set to the Stable (2.6) branch:
                              >>> Updating repositories metadata... done.
                              Your system is up to date

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                Antibiotic @barnops last edited by

                                @barnops Did you try my tip with web configurator certificate renewing?

                                R 1 Reply Last reply Reply Quote 0
                                • R
                                  rcoleman-netgate Netgate Administrator @Antibiotic last edited by

                                  @antibiotic This shouldn't have anything to do with this. The local GUI Cert is not related to repo access.

                                  --
                                  Ryan
                                  Repeat (after me): MESH IS THE DEVIL! MESH IS THE DEVIL!
                                  Requesting firmware for your Netgate device? https://go.netgate.com
                                  Switching: Mikrotik, Netgear, Extreme
                                  Wireless: Aruba, Ubiquiti

                                  A B 2 Replies Last reply Reply Quote 0
                                  • A
                                    Antibiotic @rcoleman-netgate last edited by

                                    @rcoleman-netgate roger that))))

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      barnops @rcoleman-netgate last edited by

                                      @rcoleman-netgate said in Pfsense 2.6 to plus. Unable to check:

                                      @antibiotic This shouldn't have anything to do with this. The local GUI Cert is not related to repo access.

                                      But for the record, I did.
                                      It didn't solve anything.

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        barnops @barnops last edited by

                                        This post is deleted!
                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          barnops last edited by

                                          @barnops Also, interesting that the validity dates on this cert are expired.

                                          openssl x509 -in /etc/ssl/pfSense-repo-custom.cert -text
                                          Certificate:
                                          Data:
                                          Version: 3 (0x2)
                                          Serial Number:
                                          7f:c3:e5:________________________:45:83:59:5a:08
                                          Signature Algorithm: sha256WithRSAEncryption
                                          Issuer: C = US, ST = Texas, L = Austin, O = "Rubicon Communications, LLC (Netgate)", OU = ProdTrack CA, CN = ProdTrack CA
                                          Validity
                                          Not Before: Mar 10 19:01:29 2023 GMT
                                          Not After : Mar 11 07:01:29 2023 GMT

                                          JeGr 1 Reply Last reply Reply Quote 0
                                          • JeGr
                                            JeGr LAYER 8 Moderator @barnops last edited by

                                            Perhaps related: since a reboot this morning I don't get any package repos with the following errors:

                                            ...shortened...
                                            
                                            Updating pfSense repository catalogue...
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Authentication error
                                            repository pfSense has no meta file, using default settings
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Authentication error
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com
                                            35160031232:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
                                            pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Authentication error
                                            Unable to update repository pfSense
                                            Error updating repositories!
                                            

                                            Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                                            If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

                                            1 Reply Last reply Reply Quote 0
                                            • B
                                              barnops last edited by

                                              Looks like whatever was going wrong was resolved this morning.
                                              I am now able to pull the update version.

                                              But wasn't it a requirement to swap to 22.01 first when upgrading from CE to Plus?
                                              Now 23.01 is listed when going from 2.6.0.

                                              01c7f714-0256-439d-acdf-2413d7ebd43b-image.png

                                              B 1 Reply Last reply Reply Quote 0
                                              • B
                                                barnops @barnops last edited by barnops

                                                @barnops said in Pfsense 2.6 to plus. Unable to check:

                                                Looks like whatever was going wrong was resolved this morning.
                                                I am now able to pull the update version.

                                                But wasn't it a requirement to swap to 22.01 first when upgrading from CE to Plus?
                                                Now 23.01 is listed when going from 2.6.0.

                                                01c7f714-0256-439d-acdf-2413d7ebd43b-image.png

                                                Seems like it updated properly to 23.01 with no ill effects:
                                                Removing unnecessary packages... done.
                                                Cleanup pkg cache... done.
                                                pfSense 23.01-RELEASE amd64 Fri Feb 10 20:06:33 UTC 2023
                                                Bootup complete

                                                So what ended up being the issue?

                                                1 Reply Last reply Reply Quote 0
                                                • A
                                                  Antibiotic last edited by Antibiotic

                                                  Again unable to check available packages. Please fix it!
                                                  Updating pfSense-core repository catalogue...
                                                  pkg: pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request
                                                  repository pfSense-core has no meta file, using default settings. Trying entering to https://pfsense-plus-pkg00.atx.netgate.com/ from browser and result: 400 Bad Request
                                                  No required SSL certificate was sent
                                                  nginx.

                                                  1 Reply Last reply Reply Quote 0
                                                  • First post
                                                    Last post