Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Error during new install

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    11 Posts 2 Posters 361 Views 3 Watching
    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 Offline
      murbancic
      last edited by murbancic

      I tried to upgrade to 2.9 last night and ran into an issue. I figured the fastest option would be to just re-install 2.8.1 but now I keep having an issue there. Once I get through the setup and begin the install, I get the following error:

      [1/1] Fetching pkg 1.21.3_8: .....
      pkg-static: Failed to fetch https://pkg.pfsense.org/pfSense_v2_8_1/All/pkg-1.21.3_8: Timeout wa
      

      I have tried installing 2.9 but get the same error. My WAN seems to be working when I test it on my laptop. Any advice on what the issue could be here?

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

        Seems like a general connectivity issue. Though by that point it has connected to the servers to check the repos available.

        When it fails you can drop to the shell with the existing network config in place and run some tests to see what might be failing. So ping out by IP and by FQDN for example.

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          murbancic @stephenw10
          last edited by

          @stephenw10 I am able to successfully ping 8.8.8.8 and www.google.com

          M 1 Reply Last reply Reply Quote 0
          • M Offline
            murbancic @murbancic
            last edited by

            To add to this, ping pkg.pfsense.org gives an error that says it cannot resolve address family for host and not supported.

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

              That's because it's an SRV record, it doesn't resolve directly:
              https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#packages-netgate-com-has-no-a-aaaa-record

              So:

              [26.07-RELEASE][admin@apu.stevew.lan]/root: ping pkg.pfsense.org
              ping: cannot resolve pkg.pfsense.org: Address family for hostname not supported
              [26.07-RELEASE][admin@apu.stevew.lan]/root: host -t srv _https._tcp.pkg.pfsense.org
              _https._tcp.pkg.pfsense.org has SRV record 10 10 443 pkg01-atx.netgate.com.
              _https._tcp.pkg.pfsense.org has SRV record 10 10 443 pkg00-atx.netgate.com.
              [26.07-RELEASE][admin@apu.stevew.lan]/root: ping pkg00-atx.netgate.com
              PING pkg00-atx.netgate.com (208.123.73.207): 56 data bytes
              64 bytes from 208.123.73.207: icmp_seq=0 ttl=45 time=116.956 ms
              64 bytes from 208.123.73.207: icmp_seq=1 ttl=45 time=117.286 ms
              
              1 Reply Last reply Reply Quote 0
              • stephenw10S Offline
                stephenw10 Netgate Administrator
                last edited by

                Hmm, there does seem to be some issue there though. That file path looks wrong. Checking...

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

                  Hmm, nope it's working as expected in testing here.

                  M 2 Replies Last reply Reply Quote 0
                  • M Offline
                    murbancic @stephenw10
                    last edited by

                    @stephenw10 yea so I’m able to ping both the package servers.

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      murbancic @stephenw10
                      last edited by

                      @stephenw10 any other suggestions? I’ve uploaded an image of what I am seeing.

                      IMG_3795.jpeg

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        murbancic @murbancic
                        last edited by

                        I think I have it working now. Seems to have come down to a hardware issue. I have 8 ethernet ports on my box in 2 blocks of 4. I moved the WAN to a different port on the opposed set of ports and the install progressed. I'm currently restoring from backup.

                        Everything I tried:

                        • I have 2 hard drives, tried each drive individually
                        • Physically disconnected one drive and installed
                        • Replaced CMOS battery
                        • Installation of OpenSense (this failed as well which led me to a hardware issue)
                        1 Reply Last reply Reply Quote 1
                        • stephenw10S Offline
                          stephenw10 Netgate Administrator
                          last edited by

                          Hmm, weird. Clearly not a complete connection failure. Some MTU issue perhaps?

                          For reference that should be downloadable directly as a test:

                          [26.07-RELEASE][admin@apu.stevew.lan]/tmp: fetch https://pkg00-atx.netgate.com/pfSense_v2_8_1_amd64-pfSense_v2_8_1/All/pkg-1.21.3_8.pkg
                          pkg-1.21.3_8.pkg                                        16 MB 2552 kBps    07s
                          
                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                          Privacy Policy · Cookie Policy