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

    Upgraded to ver 2.3.4 now unable to check for updates

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    8 Posts 6 Posters 1.7k 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.
    • N
      nerothecat
      last edited by

      I upgraded via GUI from 2.3.x to 2.3.4. before the upgrade I was able to check for updates and update from the GUI. I can ping both updates.pfsense.org and pfsense.org. Tracert does resolve after several hops (10-12) to both sites. I am new to pfsense device.

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

        We are seeing the same thing on 2.3.4 p1

        2.3.4-RELEASE-p1 (amd64)
        built on Fri Jul 14 14:56:00 CDT 2017
        FreeBSD 10.3-RELEASE-p19

        Unable to check for updates

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

          Same here

          2.3.4-RELEASE (amd64)
          built on Wed May 03 15:13:29 CDT 2017
          FreeBSD 10.3-RELEASE-p19

          Unable to check for updates

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Try this:

            System > Update, Update Settings

            Change the branch to Legacy 2.3.X

            Click on System Update. Some things have to update in the background so if it still errors give is a sec and click it again. You should see 2.3.5_1 available. Upgrade to that.

            When you are upgraded and restarted, go back to System > Update, Update Settings and change the branch to Latest stable version (2.4.X)

            Go back to System Updates - same thing applies. Give it time and click it again after the pkg repo updates in the background.

            You should see 2.4.2_1 available. Update to it.

            There is sort of a cart-horse thing going on at 2.3.4 (And, I think, 2.3.4_1). This was fixed in 2.3.5_1 so getting there first enables you to go to 2.4.2_1.

            If you absolutely MUST go from 2.3.4 to 2.4.2_1 in one step you can manually edit the file /etc/inc/pkg-utils.inc and change the calls to proc_open("/usr/sbin/pkg to proc_open("/usr/local/sbin/pkg-static . Don't come crying to me if you try that and screw it up.

            If, for some reason, you want to stay at 2.3.X just leave the branch set at Legacy/stable 2.3.X. That will enable packages to be installed, etc.

            I highly doubt 2.3.X will be updated past about October 2018. Almost certainly not into 2019 so upgrading to 2.4.X is pretty much necessary. A path toward that end should be charted.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              "You should see 2.4.3_1 available. Update to it."

              2.4.3_1 is available?

              I only see 2.4.3 development snapshots?

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Thanks. Sorry. 2.4.3 on the brain. Edited to correct to 2.4.2_1

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  You're fired.

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    Figured some kind of typo ;) hehehe

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

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