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

    pfSense Plus Software Version 23.05 Release Candidate Now Available

    Messages from the pfSense Team
    26
    118
    45.2k
    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.
    • GertjanG
      Gertjan @DefenderLLC
      last edited by

      @DefenderLLC Yeah .... this time I applied the finger in the nose strategy :

      I hit 'update' without any precautions.
      That is, without :
      Exporting the current config.
      Creating a ZFS snapshot
      I didn't check if I has a USB drive with the soon to be 'old' 23.05
      I didn't do the "stop - power down- start and check" test cycle.
      I didn't remove all packages before upgrading.
      I didn't check the main logs for current 'strange' behavior'.
      I didn't check if there where others users using the connection.
      I didn't check space left on my drives.
      I didn't check my UPS battery state.
      Etc. The common sense list is rather long.

      I perfectly did the " I do not read the documentation", I didn't apply the "do this before you upgrade 'list'".
      I was doing the perfect average 'kevin' that 'clicks' and assumes the consequences afterwards.

      Well ... it was a perfect upgrade, I went from the latest "23.05.1 RC" to "23.05.1" in a minute or so.

      True : I had a "23.05" ZFS snapshot waiting for me, from last week, so I could have found a stable situation with a second click.

      No "help me" PM's please. Use the forum, the community will thank you.
      Edit : and where are the logs ??

      1 Reply Last reply Reply Quote 1
      • DefenderLLCD
        DefenderLLC
        last edited by

        Hey All,

        So I noticed the 23.09 repo returned to my update page, but when I flipped it back to 23.05.1, the widget is now presenting me with a new upgrade; however, is does not appear on the actual upgrade page. I assume this is the same version I am on now as I did not actually upgrade anything. Just a couple flips the repos. All system patches were already applied. is this just a bug?

        1136f051-1af2-4c56-b604-3959bae0f42c-image.png

        06ea98bd-c106-4e04-8d76-6d06a79b4e6b-image.png

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

          Yes, there is an upstream bug in the data returned by pkg. Switching to 23.09 will have pulled in the new version which has it.
          If you need to stay on 23.05.1 I would force reinstall pkg back to version in the 23.05.1 repo. Otherwise is should be fixed in the 23.09 version shortly.

          Steve

          T 1 Reply Last reply Reply Quote 1
          • T
            tedquade @stephenw10
            last edited by

            @stephenw10 How do I force reinstall pkg back to version in the 23.05.1 repo. ?

            Ted Quade

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

              Make sure the update repo is set to 23.05.1 then run:
              pkg-static install -fy pkg

              T DefenderLLCD 2 Replies Last reply Reply Quote 1
              • T
                tedquade @stephenw10
                last edited by

                @stephenw10 Did the trick. Thanks.

                Ted Quade

                1 Reply Last reply Reply Quote 1
                • DefenderLLCD
                  DefenderLLC @stephenw10
                  last edited by

                  @stephenw10 said in pfSense Plus Software Version 23.05 Release Candidate Now Available:

                  Make sure the update repo is set to 23.05.1 then run:
                  pkg-static install -fy pkg

                  Back to normal. Thanks!

                  c71d283f-5cdd-4ac8-9cd8-6fe3c39b678d-image.png

                  B 1 Reply Last reply Reply Quote 1
                  • B
                    barindervicky89 @DefenderLLC
                    last edited by

                    @DefenderLLC

                    I had same problem. Firewall is on version 23.05.1-release.

                    1d2471f2-dc1a-4a62-9533-dcd031f72814-image.png

                    Firmware Branch also set to "Latest Stable Version (23.05.1)"

                    ecce31f1-d303-481d-8924-47b84e8a85a5-image.png

                    When I run the command "Shell Output - pkg-static install -fy pkg" from Diagnostics\Command prompt then it is giving following error:-

                    pdating pfSense-core repository catalogue...
                    pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz: Bad Request
                    repository pfSense-core has no meta file, using default settings
                    pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg: Bad Request
                    pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_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_05_1_amd64-pfSense_plus_v23_05_1/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_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg: Bad Request
                    pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz: Bad Request
                    Unable to update repository pfSense
                    Error updating repositories!
                    Execute Shell Command

                    How to fix this error. any idea. Thanks

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

                      That's not the same error. 'Bad request' like that means it's sending an invalid client certificate.

                      Try running at the CLI: pfSense-repoc what error does it return (if any)?

                      Steve

                      B 1 Reply Last reply Reply Quote 1
                      • B
                        barindervicky89 @stephenw10
                        last edited by

                        @stephenw10
                        I have clean reinstall the PFSense 2.7 and stop automatically upgrade. Now it is working

                        GertjanG 1 Reply Last reply Reply Quote 1
                        • GertjanG
                          Gertjan @barindervicky89
                          last edited by

                          @barindervicky89 said in pfSense Plus Software Version 23.05 Release Candidate Now Available:

                          and stop automatically upgrade

                          What or how did you stop that ?
                          AFAIK, pfSense doesn't auto upgrade.

                          No "help me" PM's please. Use the forum, the community will thank you.
                          Edit : and where are the logs ??

                          B 1 Reply Last reply Reply Quote 2
                          • B
                            barindervicky89 @Gertjan
                            last edited by

                            @Gertjan said in pfSense Plus Software Version 23.05 Release Candidate Now Available:

                            automatically upgrade

                            I have selected the "latest Stable Release (2.7.0) in Branch and Check mark the option "Disable the deshboard auto-upgrade Check" under System\Update\Update Setting.

                            V 1 Reply Last reply Reply Quote 0
                            • V
                              Vollans @barindervicky89
                              last edited by

                              @barindervicky89 That could be phrased better, it actually means “auto Dashboard update check”

                              1 Reply Last reply Reply Quote 0
                              • M mwatch unpinned this topic on
                              • First post
                                Last post