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

    can't update pfsense or install packages

    Scheduled Pinned Locked Moved General pfSense Questions
    148 Posts 9 Posters 30.1k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      So your firewall can't resolve hosts via DNS, you need to investigate why and fix that.

      Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      M 2 Replies Last reply Reply Quote 0
      • M
        mrrobot @jimp
        last edited by

        @jimp any idea on how ?

        1 Reply Last reply Reply Quote 0
        • M
          mrrobot @jimp
          last edited by

          @jimp i have reinstalled the system, tried different dns servers, restarted the dns resolver any of that helped

          Dobby_D 1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            https://docs.netgate.com/pfsense/en/latest/troubleshooting/dns.html

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            M 1 Reply Last reply Reply Quote 0
            • Dobby_D
              Dobby_ @mrrobot
              last edited by

              @mrrobot said in can't update pfsense or install packages:

              @jimp i have reinstalled the system, tried different dns servers, restarted the dns resolver any of that helped

              Is your WAN Gateway the default gateway?

              #~. @Dobby

              Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
              PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
              PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)

              M 1 Reply Last reply Reply Quote 0
              • M
                mrrobot @jimp
                last edited by

                @jimp said in can't update pfsense or install packages:

                https://docs.netgate.com/pfsense/en/latest/troubleshooting/dns.html

                followed the guide, everything is ok only the last part of it where i do actually have lot of blocked traffic firewall logs
                Screenshot 2023-05-27 at 10.58.31.png
                i didn't touch the firewall rules btw

                Screenshot 2023-05-27 at 11.00.15.png

                1 Reply Last reply Reply Quote 0
                • M
                  mrrobot @Dobby_
                  last edited by

                  @Dobby_ said in can't update pfsense or install packages:

                  Gateway the default gate

                  yes

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

                    @Dobby_ any ideas ?

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

                      You are still seeing DNS resolution errors?

                      Can you ping out by IP directly?

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

                        @stephenw10 yes even after a fresh install

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

                          So, yes, you are still seeing DNS errors.

                          Can you ping out by IP directly?

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

                            @stephenw10 dns resolution works fine though Screenshot 2023-06-20 at 08.52.48.png

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

                              @stephenw10 Screenshot 2023-06-20 at 20.57.54.png

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

                                So what do you see if you run?: pkg-static -d update

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

                                  @stephenw10 said in can't update pfsense or install packages:
                                  for some reason i cant put all the code, it gets reported as spam so i put the end of it

                                  pkg-static -d update

                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.conf with opts "i"
                                  DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz
                                  DBG(1)[94031]> opening libfetch fetcher
                                  DBG(1)[94031]> Fetch > libfetch: connecting
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz with opts "i"
                                  pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/meta.txz: No route to host
                                  repository pfSense has no meta file, using default settings
                                  DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg
                                  DBG(1)[94031]> opening libfetch fetcher
                                  DBG(1)[94031]> Fetch > libfetch: connecting
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg with opts "i"
                                  pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.pkg: No route to host
                                  DBG(1)[94031]> Request to fetch pkg+https://packages.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz
                                  DBG(1)[94031]> opening libfetch fetcher
                                  DBG(1)[94031]> Fetch > libfetch: connecting
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
                                  DBG(1)[94031]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz with opts "i"
                                  pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_6_0_amd64-pfSense_v2_6_0/packagesite.txz: No route to host
                                  Unable to update repository pfSense
                                  Error updating repositories!
                                  [2.6.0-RELEASE][admin@xxxxx]/root:
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    @mrrobot said in can't update pfsense or install packages:

                                    No route to host

                                    Ok, so it has no route. Check Diag > Routes. Make sure there's a valid default route.

                                    Steve

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

                                      @stephenw10 how do i know that the default route is valid ?

                                      my wan interface ip is the one ending with 228 and its a public ip

                                      looks like my isp giving me x.x.x.228 defaulting to a x.x.x.229 gateway

                                      Screenshot 2023-06-21 at 00.07.05.png

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

                                        That looks valid. Does the gateway show as up?

                                        Do you have an IPv6 address on any interfaces?
                                        It could be trying to use IPv6. Try setting 'Prefer IPv4' in Sys > Adv > Networking.

                                        Steve

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

                                          @stephenw10 thank you
                                          Gateway looks fine & Prefer IPv4 over IPv6 is checked

                                          Screenshot 2023-06-21 at 07.56.37.png

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

                                            And it's still failing with 'no route'?

                                            It could be something upstream returning no-route. Try to ping pkg01-atx.netgate.com directly.

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