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

can't update pfsense or install packages

General pfSense Questions
9
148
27.0k
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
    stephenw10 Netgate Administrator
    last edited by Jul 25, 2023, 1:59 PM

    Hmm, so back to the initial error then?

    You've had three separate errors here.
    What changed to get back to the first error? Can you resolve things locally? Are you running Unbound in resolving mode without DoT?

    M 1 Reply Last reply Jul 25, 2023, 6:30 PM Reply Quote 0
    • M
      mrrobot @stephenw10
      last edited by Jul 25, 2023, 6:30 PM

      @stephenw10 nothing to my knowledge

      1 Reply Last reply Reply Quote 0
      • S
        stephenw10 Netgate Administrator
        last edited by Jul 25, 2023, 9:54 PM

        Spontaneously producing three different failure types has pretty much got to be something upstream changing the connection.

        1 Reply Last reply Reply Quote 0
        • L
          Leonardo 5
          last edited by Leonardo 5 Aug 8, 2023, 7:15 PM Aug 8, 2023, 6:46 PM

          Oh my God, you don't know how many hours it took me to find a solution. I was getting that "no route to host" and "no address record" error on updating packages and it was solved when I changed the DNS Resolution Behaviour to "Use remote DNS Servers, ignore local DNS".
          login-to-view

          1 Reply Last reply Reply Quote 0
          • L
            Leonardo 5
            last edited by Leonardo 5 Aug 8, 2023, 7:20 PM Aug 8, 2023, 7:20 PM

            The problem was solved temporarily, now the situation is the same as before, I didn't change anything. I was able to run the pkg-static -d update, but now it is showing "no route to host" again and I can not download packages.

            Running "nc -vz4 pkg00-atx.netgate.com 443" gives me the following result:
            connect to pkg00-atx.netgate.com port 443 (tcp) failed: Can't assign requested address

            1 Reply Last reply Reply Quote 0
            • S
              stephenw10 Netgate Administrator
              last edited by Aug 8, 2023, 9:21 PM

              Does it actually have a route? IPv4?

              'Can't assign address' seems more like a conflict somewhere.

              L 1 Reply Last reply Aug 9, 2023, 1:31 PM Reply Quote 0
              • L
                Leonardo 5 @stephenw10
                last edited by Leonardo 5 Aug 9, 2023, 1:35 PM Aug 9, 2023, 1:31 PM

                @stephenw10 It has a route.
                179.16.0.1 is a mikrotik router, we are using it only for WAN connection, it doesn't have any special configuration. 179.16.0.4 is the PfSense LAN IP.
                login-to-view

                When I run traceroute on pkg01-atx.netgate.com, it shows:
                1 179.16.0.1 0.323 ms 0.174 ms 0.200 ms
                2 X.X.X.254 0.451 ms 0.672 ms 1.015 ms
                3 Y.Y.Y.41 1.147 ms 0.848 ms 0.995 ms
                4 A.A.A.213 2.372 ms 1.907 ms 1.979 ms
                5 * * *
                6 62.115.164.218 82.134 ms 81.618 ms 81.608 ms
                7 * * *
                8 * * *
                9 4.14.49.2 117.047 ms 117.061 ms 117.034 ms
                10 64.20.229.166 117.057 ms 116.926 ms 117.031 ms
                11 66.219.34.198 116.789 ms 116.812 ms
                66.219.34.194 117.138 ms
                12 208.123.73.4 117.534 ms 117.299 ms 117.631 ms
                13 * * *
                14 * * *
                15 * * *
                16 * * *
                17 * * *
                18 * * *

                It seems that looking at the route it does not reach the destination point. But I find it strange, because I can ping.
                PING pkg01-atx.netgate.com (208.123.73.209): 56 data bytes
                64 bytes from 208.123.73.209: icmp_seq=0 ttl=50 time=117.575 ms
                64 bytes from 208.123.73.209: icmp_seq=1 ttl=50 time=117.406 ms
                64 bytes from 208.123.73.209: icmp_seq=2 ttl=50 time=117.492 ms

                --- pkg01-atx.netgate.com ping statistics ---
                3 packets transmitted, 3 packets received, 0.0% packet loss
                round-trip min/avg/max/stddev = 117.406/117.491/117.575/0.069 ms

                1 Reply Last reply Reply Quote 0
                • S
                  stephenw10 Netgate Administrator
                  last edited by Aug 9, 2023, 1:50 PM

                  Use ICMP traceroute like: traceroute -In pkg01-atx.netgate.com

                  L 1 Reply Last reply Aug 9, 2023, 2:04 PM Reply Quote 0
                  • L
                    Leonardo 5 @stephenw10
                    last edited by Aug 9, 2023, 2:04 PM

                    @stephenw10 traceroute -In pkg01-atx.netgate.com result:
                    traceroute to pkg01-atx.netgate.com (208.123.73.209), 64 hops max, 48 byte packets
                    1 179.16.0.1 0.402 ms 1.035 ms 0.310 ms
                    2 X.X.X.254 1.407 ms 0.476 ms 0.777 ms
                    3 Y.Y.Y.41 1.907 ms 0.760 ms 0.986 ms
                    4 * * *
                    5 * * *
                    6 62.115.164.218 82.548 ms 81.724 ms 82.015 ms
                    7 * * *
                    8 * * *
                    9 4.14.49.2 118.087 ms 117.059 ms 116.963 ms
                    10 64.20.229.158 117.777 ms 117.279 ms 117.157 ms
                    11 66.219.34.194 117.218 ms 117.743 ms 116.793 ms
                    12 208.123.73.4 118.006 ms 117.298 ms 118.029 ms
                    13 208.123.73.209 117.889 ms 117.300 ms 117.119 ms

                    1 Reply Last reply Reply Quote 0
                    • S
                      stephenw10 Netgate Administrator
                      last edited by Aug 9, 2023, 2:06 PM

                      But you're still seeing 'no route to host' in the output of: pkg-static -d update ?

                      L 1 Reply Last reply Aug 9, 2023, 2:32 PM Reply Quote 0
                      • L
                        Leonardo 5 @stephenw10
                        last edited by Aug 9, 2023, 2:32 PM

                        @stephenw10 Yes. And I can not see/download packages.
                        login-to-view

                        On running pkg-static -d update:
                        DBG(1)[97999]> pkg initialized
                        Updating pfSense-core repository catalogue...
                        DBG(1)[97999]> PkgRepo: verifying update for pfSense-core
                        DBG(1)[97999]> PkgRepo: need forced update of pfSense-core
                        DBG(1)[97999]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
                        DBG(1)[97999]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.conf
                        DBG(1)[97999]> opening libfetch fetcher
                        DBG(1)[97999]> Fetch > libfetch: connecting
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.conf with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.conf with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.conf with opts "i"
                        DBG(1)[97999]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.txz
                        DBG(1)[97999]> opening libfetch fetcher
                        DBG(1)[97999]> Fetch > libfetch: connecting
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.txz with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.txz with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.txz with opts "i"
                        pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.txz: No route to host
                        repository pfSense-core has no meta file, using default settings
                        ...
                        DBG(1)[97999]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz
                        DBG(1)[97999]> opening libfetch fetcher
                        DBG(1)[97999]> Fetch > libfetch: connecting
                        DBG(1)[97999]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i"
                        DBG(1)[97999]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i"
                        pkg-static: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz: No route to host
                        Unable to update repository pfSense
                        Error updating repositories!

                        1 Reply Last reply Reply Quote 0
                        • S
                          stephenw10 Netgate Administrator
                          last edited by Aug 9, 2023, 2:37 PM

                          Hmm, try: pkg-static -d4 update

                          L 1 Reply Last reply Aug 9, 2023, 2:41 PM Reply Quote 0
                          • L
                            Leonardo 5
                            last edited by Aug 9, 2023, 2:38 PM

                            When I changed DNS Resolution Behavior to "Use remote DNS Servers, ignore local DNS" I was able to see the packages and run "pkg-static -d update".
                            I even tried to install the open vpn config export package, but I got an error asking to update pfsense.
                            It was only normal for about 10 minutes, then when I tried to update pfSense it was back to the same problem as before, "no route to host".

                            M 1 Reply Last reply Aug 9, 2023, 3:38 PM Reply Quote 0
                            • L
                              Leonardo 5 @stephenw10
                              last edited by Aug 9, 2023, 2:41 PM

                              @stephenw10 Running pkg-static -d4 update
                              ...
                              DBG(1)[10184]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz
                              DBG(1)[10184]> opening libfetch fetcher
                              DBG(1)[10184]> Fetch > libfetch: connecting
                              DBG(1)[10184]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i4"
                              DBG(1)[10184]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i4"
                              DBG(1)[10184]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i4"
                              pkg-static: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz: Permission denied
                              Unable to update repository pfSense
                              Error updating repositories!

                              1 Reply Last reply Reply Quote 0
                              • S
                                stephenw10 Netgate Administrator
                                last edited by Aug 9, 2023, 3:20 PM

                                Ok so it looks like it's trying to use v6 by default but there's no route. And something is blocking it when it tries to use v4.

                                Are you logged in as admin/root?

                                Do you have outbound block rules? pfBlocker? Snort?

                                L 1 Reply Last reply Aug 9, 2023, 4:11 PM Reply Quote 0
                                • M
                                  mrrobot @Leonardo 5
                                  last edited by Aug 9, 2023, 3:38 PM

                                  @Leonardo-5 in which country you are using ur pfsense router ? i have the same issue as u & we suspect the isp is blocking the traffic !

                                  L 1 Reply Last reply Aug 9, 2023, 4:02 PM Reply Quote 0
                                  • L
                                    Leonardo 5 @mrrobot
                                    last edited by Leonardo 5 Aug 9, 2023, 4:17 PM Aug 9, 2023, 4:02 PM

                                    @mrrobot Brazil. I'm starting to suspect that the ISP may be the cause of the problem indeed.

                                    M 1 Reply Last reply Aug 9, 2023, 5:57 PM Reply Quote 0
                                    • L
                                      Leonardo 5 @stephenw10
                                      last edited by Aug 9, 2023, 4:11 PM

                                      @stephenw10 My ISP doesn't support ipv6. At networking config the parameter "Prefer IPv4 over IPv6" is checked. I am logged as admin when accessing from browser.
                                      I am using PfSense on a virtual machine (I plan to buy a Netgate appliance when possible) and running the command as root gives me the same result.
                                      Outbound NAT mode is automatic, I did not add any rule. I am using pfSense with default settings, then I am not using pfBlocker or Snort.
                                      login-to-view

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        stephenw10 Netgate Administrator
                                        last edited by Aug 9, 2023, 5:55 PM

                                        Try running a packet capture on WAN when you are trying to check. Filter by our subnet 208.123.73.0/24.
                                        Make sure you see traffic leavning for the pkg servers at 208.123.73.207 or .209.
                                        If something upstream is blocking that you should see that in a reply since it shows 'permission denied'

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mrrobot @Leonardo 5
                                          last edited by Aug 9, 2023, 5:57 PM

                                          @Leonardo-5 its gonna be complecated updating or installing packages in this case 😭

                                          L 1 Reply Last reply Aug 9, 2023, 6:06 PM Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.