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

    To 23.05 or not ? that is the question :)

    Scheduled Pinned Locked Moved
    General pfSense Questions
    27
    41
    8.8k
    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.
    • S
      sgw @Negan
      last edited by

      Upgraded my own SG1100 yesterday without issues.

      Small PHP-related crash log at first login, but everthing works so far. Visible change: less RAM usage! From ~75% to 50%, nice.

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        To 23.05 or not ? that is the question :)

        pfSense 23.05 on a 4100 : it was a click, a coffee, and done.

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

        M 1 Reply Last reply Reply Quote 1
        • R
          renegade
          last edited by

          Updated my 4100 wit activated RAM disk.
          made a second reboot after the update and everything works smooth.
          Had to apply a small config change for my apc ups, which was not recognized.

          1 Reply Last reply Reply Quote 0
          • F
            fastfwd @keyser
            last edited by

            @chudak Same cert failure as @keyser on my XG-7100, same method to resolve.

            1 Reply Last reply Reply Quote 0
            • M
              mvikman
              last edited by mvikman

              Non-Netgate hardware updated first from 23.01 to 23.05 RCs up to 23.05.r.20230519.0600.
              After seeing some problems with r.20230522.1252 changed branch back to "Current Stable 23.01" and waited for "Current Stable 23.05" to become available.
              No problems updating to 23.05 Release, though I'm not running any special packages.

              pfSense Plus 24.11-RELEASE (amd64)
              Dell Optiplex 7040 SFF
              Core i5-6500, 8GB RAM, 2x 240GB SSD (ZFS Mirror)
              HPE 561T (X540-AT2), 2-port 10Gb RJ45
              HPE 562SFP+ (X710-DA2), 2-port 10Gb SFP+

              4 1 Reply Last reply Reply Quote 0
              • 4
                4o4rh @mvikman
                last edited by

                @mvikman create a backup and download a local copy in case you have to do a full reinstall.

                when you kick off, go have coffee. the rebooting in 10s is way understated in my experience. needed 2-3min before the reboot, and then you still have a minute or so for the update to run

                M 1 Reply Last reply Reply Quote 0
                • M
                  mvikman @4o4rh
                  last edited by

                  @gwaitsi I save the config file to my pc everytime I make changes.
                  I always do a reboot before upgrade and I follow reboots/upgrades from console(display).
                  I also have a backup pfsense box that I can swap in to use if the main one dies.

                  pfSense Plus 24.11-RELEASE (amd64)
                  Dell Optiplex 7040 SFF
                  Core i5-6500, 8GB RAM, 2x 240GB SSD (ZFS Mirror)
                  HPE 561T (X540-AT2), 2-port 10Gb RJ45
                  HPE 562SFP+ (X710-DA2), 2-port 10Gb SFP+

                  1 Reply Last reply Reply Quote 0
                  • RobbieTTR
                    RobbieTT
                    last edited by RobbieTT

                    Updated my 6100 Max:

                    • Backed-up config
                    • Set a ZFS Boot Environment snapshot
                    • Pre-booted
                    • Clicked on the update icon
                    • Auto rebooted with zero issues

                    So yes, I left all packages in place and other than setting backups (thankfully not needed) and the pre-booting I did nothing more than allow pfSense to sort it all out. Which it did.

                    ☕️

                    1 Reply Last reply Reply Quote 0
                    • P
                      psp
                      last edited by

                      Upgraded successfully here, XG-1537 in HA. First the backup unit, then the master.
                      Using pfBlockerNG and zabbix-agent6.

                      1 Reply Last reply Reply Quote 0
                      • S
                        SteveITS Rebel Alliance @chudak
                        last edited by

                        @chudak One patch so far, for the bleeding-edgers :)
                        https://forum.netgate.com/topic/180313/firewall-alias-import-bug-after-upgrade-to-23-05-release-amd64

                        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
                        • T
                          tman222
                          last edited by

                          Successfully upgraded two systems (one Xeon D based Supermicro unit and one Intel i3 custom build) from 23.01 to 23.05. Overall, the upgrade went smooth and was fairly quick on both systems.

                          A minor issue was that both systems ran into the certificate error the first time when trying to upgrade (as has been documented in other threads already), but flipping the Branch back to 23.01 and then forward to 23.05 again under System -> Update allowed the upgrade to proceed the second time.

                          Very excited to see IPsec Multi-Buffer (IPsec-MB) Cryptographic Acceleration being added in this release as well as a formal pfSense package for udpbroadcastrelay.

                          A big Thank You to everyone who contributed to this release for all hard work and effort.

                          1 Reply Last reply Reply Quote 0
                          • JonathanLeeJ
                            JonathanLee @chudak
                            last edited by

                            @chudak pull the trigger . . . upgrade, it was so smooth for me.

                            Make sure to upvote

                            1 Reply Last reply Reply Quote 0
                            • C
                              Cylosoft
                              last edited by

                              We did about a dozen boxes. Went great. No issues at all. Hoping the syslog-ng issue gets sorted out soon so we can do a bunch more.

                              JonathanLeeJ 1 Reply Last reply Reply Quote 3
                              • JonathanLeeJ
                                JonathanLee @Cylosoft
                                last edited by

                                @Cylosoft I updated my little SG-2100MAX I got to learn with in school with and it was like a hot knife in butter in a butter bell. Just smooth. I was impressed versus the 21.01 update that one well it had some problems.

                                Make sure to upvote

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  sgw @JonathanLee
                                  last edited by

                                  Any 7100 done already?

                                  And yes: thanks to everyone who contributed to this new release!

                                  G 1 Reply Last reply Reply Quote 0
                                  • chudakC
                                    chudak @keyser
                                    last edited by

                                    @keyser

                                    That was very useful, thx!
                                    I got that too

                                    >>> Updating repositories metadata... 
Updating pfSense-core 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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/meta.txz: Authentication error
repository pfSense-core 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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.txz: Authentication error
Unable to update repository pfSense-core
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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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
34938040320:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Authentication error
Unable to update repository pfSense
Error updating repositories!
ERROR: It was not possible to determine pfSense-upgrade remote version
ERROR: It was not possible to determine pfSense-upgrade remote version
>>> Upgrading pfSense-upgrade... failed.
                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      johan333
                                      last edited by

                                      Updated from 23.01 to 23.05 on two model 2100 units. One went smooth and the other I got the certificate failure, so I followed @keyser post and successfully upgraded the other. It may be premature as the upgrade happened only 6 hours ago, but it looks like the memory leak issue has been resolved.

                                      Screenshot 2023-05-26 055121.jpg
                                      Screenshot 2023-05-26 055256.jpg
                                      Note: upgraded to 23.01 on 4-13-23

                                      1 Reply Last reply Reply Quote 1
                                      • M
                                        mer @Gertjan
                                        last edited by

                                        @Gertjan said in To 23.05 or not ? that is the question :):

                                        pfSense 23.05 on a 4100 : it was a click, a coffee, and done.

                                        This made me laugh and think "The way all upgrades should be. No issues but long enough to have a coffee"

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          PhlMike
                                          last edited by PhlMike

                                          I had gotten hit with the cert issues on my SG3100 running 23.01 when I first tried. So I found a quick ssh fix on here and I upgraded just fine. No issues so far. I have a fairly complex config.

                                          That was my home firewall.

                                          The other triple digit worth of work firewalls, I'm going to wait a little bit. we'll see if there is a 23.05.1 or something.

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            terryzb
                                            last edited by

                                            On my home 2100 I saved a config locally, pre-booted, then via the console attempted to update but was stopped by the certificate error. Searching in the Upgrades forum here I followed the advice to swap the update branch back and forth. Did another pre-boot, then updated via console went fine. Less than 10 minutes on the 2100. Did a post-install reboot for good measure. I did not uninstall pfBlockerNG or Avahi first. So far so good.

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