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

Unable to update repository pfSense

General pfSense Questions
7
39
5.5k
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.
  • B
    bmeeks
    last edited by bmeeks Sep 30, 2023, 1:58 PM Sep 30, 2023, 1:53 PM

    @yon-0 said in Unable to update repository pfSense:

    Impossible to get the value from Last-Modified HTTP header

    This error message: pkg-static: Impossible to get the value from Last-Modified HTTP header, apparently is due to a bug in one of the support libraries used by the pkg and pkg-static utilities. That bug report is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273580. I don't know if the fixed referenced in the bug report has been pulled into the pfSense branch or not.

    1 Reply Last reply Reply Quote 1
    • S
      stephenw10 Netgate Administrator
      last edited by Sep 30, 2023, 1:57 PM

      Hmm, let me check. That might have been since our large merge.

      Y 1 Reply Last reply Sep 30, 2023, 2:40 PM Reply Quote 0
      • Y
        yon 0 @stephenw10
        last edited by yon 0 Sep 30, 2023, 2:41 PM Sep 30, 2023, 2:40 PM

        @stephenw10

        pfSense-upgrade -c -d
        ERROR: It was not possible to determine pkg remote version
        >>> Updating repositories metadata...
        Updating pfSense-core repository catalogue...
        pfSense-core repository is up to date.
        Updating pfSense repository catalogue...
        Fetching meta.conf: . done
        Fetching packagesite.pkg: .......... done
        Processing entries: .......... done
        pfSense repository update completed. 725 packages processed.
        All repositories are up to date.
        23.09.a.20230929.2350 version of pfSense is available
        [23.09-DEVELOPMENT][admin@]/root: pfSense-upgrade -dy
        >>> Updating repositories metadata...
        Updating pfSense-core repository catalogue...
        Fetching meta.conf: . done
        Fetching packagesite.pkg: . done
        Processing entries: . done
        pfSense-core repository update completed. 4 packages processed.
        Updating pfSense repository catalogue...
        Fetching meta.conf: . done
        Fetching packagesite.pkg: .......... done
        Processing entries: .......... done
        pfSense repository update completed. 725 packages processed.
        All repositories are up to date.
        >>> Removing vital flag from php82...
        >>> Downloading upgrade packages...
        Updating pfSense-core repository catalogue...
        pfSense-core repository is up to date.
        Updating pfSense repository catalogue...
        Fetching meta.conf:
        pfSense repository is up to date.
        All repositories are up to date.
        Checking for upgrades (6 candidates): ...... done
        Processing candidates (6 candidates): ...... done
        The following 6 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        	pfSense-base: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-boot: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-default-config: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        	pfSense-kernel-pfSense: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-repo: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        
        Number of packages to be upgraded: 6
        
        166 MiB to be downloaded.
        [1/6] Fetching pfSense-base-23.09.a.20230929.2350.pkg: .
        pkg-static: cached package pfSense-base-23.09.a.20230929.2350: missing or size mismatch, fetching from remote
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        [23.09-DEVELOPMENT][admin@]/root: pfSense-upgrade -dy
        >>> Setting vital flag on php82...
        >>> Updating repositories metadata...
        Updating pfSense-core repository catalogue...
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        Fetching meta.txz: . done
        Fetching packagesite.pkg: . done
        Processing entries: . done
        pfSense-core repository update completed. 4 packages processed.
        Updating pfSense repository catalogue...
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        Fetching meta.txz: . done
        Fetching packagesite.pkg: ......... done
        Processing entries: .......... done
        pfSense repository update completed. 725 packages processed.
        All repositories are up to date.
        >>> Removing vital flag from php82...
        >>> Downloading upgrade packages...
        Updating pfSense-core repository catalogue...
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        repository pfSense-core has no meta file, using default settings
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        Unable to update repository pfSense-core
        Updating pfSense repository catalogue...
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        repository pfSense has no meta file, using default settings
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        Unable to update repository pfSense
        Error updating repositories!
        [23.09-DEVELOPMENT][admin@]/root: pfSense-upgrade -dy
        >>> Setting vital flag on php82...
        ERROR: It was not possible to determine pkg remote version
        >>> Updating repositories metadata...
        Updating pfSense-core repository catalogue...
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        pkg-static: An error occured while fetching package
        pkg-static: Impossible to get the value from Last-Modified HTTP header
        repository pfSense-core has no meta file, using default settings
        Fetching packagesite.pkg: . done
        Processing entries: . done
        pfSense-core repository update completed. 4 packages processed.
        Updating pfSense repository catalogue...
        Fetching meta.conf: . done
        Fetching packagesite.pkg: ........ done
        Processing entries: .......... done
        pfSense repository update completed. 725 packages processed.
        All repositories are up to date.
        >>> Removing vital flag from php82...
        >>> Downloading upgrade packages...
        Updating pfSense-core repository catalogue...
        pfSense-core repository is up to date.
        Updating pfSense repository catalogue...
        Fetching meta.conf:
        pfSense repository is up to date.
        All repositories are up to date.
        Checking for upgrades (6 candidates): ...... done
        Processing candidates (6 candidates): ...... done
        The following 6 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        	pfSense-base: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-boot: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-default-config: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        	pfSense-kernel-pfSense: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        	pfSense-repo: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense]
        
        Number of packages to be upgraded: 6
        
        166 MiB to be downloaded.
        [1/6] Fetching pfSense-base-23.09.a.20230929.2350.pkg: .......... done
        [2/6] Fetching pfSense-default-config-23.09.a.20230929.2350.pkg: . done
        [3/6] Fetching pfSense-23.09.a.20230929.2350.pkg: .......... done
        [4/6] Fetching pfSense-boot-23.09.a.20230929.2350.pkg: .......... done
        [5/6] Fetching pfSense-repo-23.09.a.20230929.2350.pkg: . done
        [6/6] Fetching pfSense-kernel-pfSense-23.09.a.20230929.2350.pkg: .......... done
        Checking integrity... done (0 conflicting)
        >>> Downloading pkg...
        
        No packages are required to be fetched.
        Integrity check was successful.
        >>> Upgrading pfSense-boot...>>> Unmounting /boot/efi...
        umount: /boot/efi: not a file system root directory
         done.
        >>> Upgrading pfSense kernel...
        Checking integrity... done (0 conflicting)
        The following 1 package(s) will be affected (of 0 checked):
        
        Installed packages to be UPGRADED:
        	pfSense-kernel-pfSense: 23.09.a.20230929.1307 -> 23.09.a.20230929.2350 [pfSense-core]
        
        Number of packages to be upgraded: 1
        [1/1] Upgrading pfSense-kernel-pfSense from 23.09.a.20230929.1307 to 23.09.a.20230929.2350...
        [1/1] Extracting pfSense-kernel-pfSense-23.09.a.20230929.2350: .......... done
        ===> Keeping a copy of current kernel in /boot/kernel.old
        >>> Removing unnecessary packages...
        Checking integrity... done (0 conflicting)
        Nothing to do.
        System is going to be upgraded.  Rebooting in 10 seconds.
        
        Broadcast Message from admin@
                (/dev/pts/0) at 16:40 CST...
        
        System is going to be upgraded.  Rebooting in 10 seconds.
        
        [23.09-DEVELOPMENT][admin@]/root: Backing up RAM disk contents
        Saving Alias Tables to RAM disk store...done.
        Saving RRD to RAM disk store...done.
        Saving DHCP Leases to RAM disk store...done.
        Saving Logs to RAM disk store...done.
        net.inet.carp.allow: 0 -> 0
        Connection closing...Socket close.
        
        Connection closed by foreign host.
        
        Disconnected from remote host(192.168.101.91) at 16:40:46.
        
        1 Reply Last reply Reply Quote 0
        • S
          stephenw10 Netgate Administrator
          last edited by Sep 30, 2023, 3:15 PM

          Mmm, it still looks like some intermittent connectivity.

          Do you see a difference between IPv4 and IPv6?
          pfSense-upgrade -dc6 vs pfSense-upgrade -dc4

          Y 4 Replies Last reply Oct 4, 2023, 10:46 AM Reply Quote 0
          • Y
            yon 0 @stephenw10
            last edited by yon 0 Oct 4, 2023, 10:46 AM Oct 4, 2023, 10:46 AM

            @stephenw10

            pfSense-upgrade -dc6
            >>> Setting vital flag on php82...
            >>> Updating repositories metadata...
            Updating pfSense-core repository catalogue...
            pkg-static: An error occured while fetching package
            pkg-static: Impossible to get the value from Last-Modified HTTP header
            pfSense-core repository is up to date.
            Updating pfSense repository catalogue...
            Fetching meta.conf:
            pfSense repository is up to date.
            All repositories are up to date.
            23.09.a.20231003.0600 version of pfSense is available
            
            1 Reply Last reply Reply Quote 0
            • Y
              yon 0 @stephenw10
              last edited by Oct 4, 2023, 10:48 AM

              @stephenw10

              pfSense-upgrade -dc4
              >>> Updating repositories metadata...
              Updating pfSense-core repository catalogue...
              pfSense-core repository is up to date.
              Updating pfSense repository catalogue...
              Fetching meta.conf:
              pkg-static: An error occured while fetching package
              pkg-static: Impossible to get the value from Last-Modified HTTP header
              pfSense repository is up to date.
              All repositories are up to date.
              23.09.a.20231003.0600 version of pfSense is available
              
              1 Reply Last reply Reply Quote 0
              • Y
                yon 0 @stephenw10
                last edited by Oct 4, 2023, 10:51 AM

                @stephenw10

                pfSense-upgrade -dy
                >>> Updating repositories metadata...
                Updating pfSense-core repository catalogue...
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                repository pfSense-core has no meta file, using default settings
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                Unable to update repository pfSense-core
                Updating pfSense repository catalogue...
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                pkg-static: An error occured while fetching package
                pkg-static: Impossible to get the value from Last-Modified HTTP header
                repository pfSense has no meta file, using default settings
                
                1 Reply Last reply Reply Quote 0
                • Y
                  yon 0 @stephenw10
                  last edited by Oct 5, 2023, 4:34 PM

                  @stephenw10

                  
                  [23.09-DEVELOPMENT][admin@pf.xiaoyu.net]/root: pfSense-upgrade -dc6
                  ERROR: It was not possible to determine pkg remote version
                  >>> Updating repositories metadata...
                  Updating pfSense-core repository catalogue...
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  repository pfSense-core has no meta file, using default settings
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  Unable to update repository pfSense-core
                  Updating pfSense repository catalogue...
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  repository pfSense has no meta file, using default settings
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  Unable to update repository pfSense
                  Error updating repositories!
                  ERROR: It was not possible to determine pfSense remote version
                  ERROR: It was not possible to determine pfSense-base remote version
                  ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
                  Your system is up to date
                  
                  pfSense-upgrade -dc4
                  ERROR: It was not possible to determine pkg remote version
                  >>> Updating repositories metadata...
                  Updating pfSense-core repository catalogue...
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  repository pfSense-core has no meta file, using default settings
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  Unable to update repository pfSense-core
                  Updating pfSense repository catalogue...
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  repository pfSense has no meta file, using default settings
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  pkg-static: An error occured while fetching package
                  pkg-static: Impossible to get the value from Last-Modified HTTP header
                  Unable to update repository pfSense
                  Error updating repositories!
                  ERROR: It was not possible to determine pfSense remote version
                  ERROR: It was not possible to determine pfSense-base remote version
                  ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
                  Your system is up to date
                  
                  1 Reply Last reply Reply Quote 0
                  • E
                    elvisimprsntr
                    last edited by elvisimprsntr Feb 8, 2025, 2:41 PM Feb 8, 2025, 2:38 PM

                    Sry to resurrect a zombie thread, but can't retrieve packages.

                    GUI just pinwheels, so I ran the suggested command below.

                    [2.7.2-RELEASE][root@pfSense.[redacted].com]/root: pkg update
                    Updating pfSense-core repository catalogue...
                    pkg: No SRV record found for the repo 'pfSense-core'
                    
                    
                    [2.7.2-RELEASE][root@pfSense.[redacted].com]/root: pkg-static -d update
                    DBG(1)[29255]> pkg initialized
                    Updating pfSense-core repository catalogue...
                    DBG(1)[29255]> PkgRepo: verifying update for pfSense-core
                    DBG(1)[29255]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
                    DBG(1)[29255]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
                    DBG(1)[29255]> curl_open
                    pkg-static: No SRV record found for the repo 'pfSense-core'
                    DBG(1)[29255]> Fetch: fetcher used: pkg+https
                    DBG(1)[29255]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
                    
                    DBG(1)[29255]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
                    
                    DBG(1)[29255]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf, left retry 3
                    
                    * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults
                    * Resolving timed out after 30005 milliseconds
                    
                    
                    patient0P 1 Reply Last reply Feb 8, 2025, 2:45 PM Reply Quote 0
                    • patient0P
                      patient0 @elvisimprsntr
                      last edited by Feb 8, 2025, 2:45 PM

                      @elvisimprsntr can you resolve other domain names?

                      E 1 Reply Last reply Feb 8, 2025, 2:50 PM Reply Quote 0
                      • E
                        elvisimprsntr @patient0
                        last edited by elvisimprsntr Feb 8, 2025, 2:52 PM Feb 8, 2025, 2:50 PM

                        @patient0

                        From clients, yes.

                        From pfSense GUI or CLI, no.

                        Using Q9 for upstream DNS

                        patient0P S 2 Replies Last reply Feb 8, 2025, 3:00 PM Reply Quote 0
                        • patient0P
                          patient0 @elvisimprsntr
                          last edited by Feb 8, 2025, 3:00 PM

                          @elvisimprsntr said in Unable to update repository pfSense:

                          From pfSense GUI or CLI, no.
                          Using Q9 for upstream DNS

                          How have you configured DNS, resolver or forward? And your clients use pfSense for DNS lookup?

                          E 1 Reply Last reply Feb 8, 2025, 3:07 PM Reply Quote 0
                          • S
                            SteveITS Galactic Empire @elvisimprsntr
                            last edited by Feb 8, 2025, 3:03 PM

                            @elvisimprsntr If forwarding, ensure DNSSEC is disabled.

                            Any restrictions on unbound or is it set to listen on All interfaces?

                            I would next restart DNS Resolver/unbound, or maybe pfSense.

                            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
                            • E
                              elvisimprsntr @patient0
                              last edited by elvisimprsntr Feb 8, 2025, 3:15 PM Feb 8, 2025, 3:07 PM

                              @patient0

                              1. DNS Resolver
                              2. Yes Clients use pfSense

                              I tried starting unbound. same issue.
                              I remotely rebooted my fiber modem (NVG599), and released and renewed WAN interface.

                              Seems to be working again.

                              Running 2.7.2 with all the latest patches.

                              This just started happening since I applied the latest swath of patches.

                              It is behaving like something on pfSense crashed or stops working.

                              @SteveITS

                              When I disable DNSSEC can't resolve static mappings.

                              https://forum.netgate.com/topic/196269/att-fiber-dns-issue/13

                              patient0P 1 Reply Last reply Feb 8, 2025, 3:16 PM Reply Quote 0
                              • patient0P
                                patient0 @elvisimprsntr
                                last edited by Feb 8, 2025, 3:16 PM

                                @elvisimprsntr said in Unable to update repository pfSense:

                                This just started happening since I applied the latest swath of patches.

                                I know it is obvious but I'd revert patches regarding unbound and see what happens.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  stephenw10 Netgate Administrator
                                  last edited by Feb 8, 2025, 3:43 PM

                                  Are clients, which can resolve, using pfSense for DNS or being passed quad9 to use directly?

                                  What is the DNS behaviour setting in General Setup?

                                  E 1 Reply Last reply Feb 8, 2025, 3:53 PM Reply Quote 0
                                  • E
                                    elvisimprsntr @stephenw10
                                    last edited by Feb 8, 2025, 3:53 PM

                                    @stephenw10 said in Unable to update repository pfSense:

                                    Are clients, which can resolve, using pfSense for DNS or being passed quad9 to use directly?

                                    Client are served pfSense LAN IP address

                                    What is the DNS behaviour setting in General Setup?

                                    login-to-view

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      stephenw10 Netgate Administrator
                                      last edited by Feb 8, 2025, 7:11 PM

                                      Hmm, and Diag > DNS Lookup just fails for all configured severs? For any fqdn?

                                      E 1 Reply Last reply Feb 8, 2025, 11:33 PM Reply Quote 0
                                      • E
                                        elvisimprsntr @stephenw10
                                        last edited by elvisimprsntr Feb 8, 2025, 11:41 PM Feb 8, 2025, 11:33 PM

                                        @stephenw10

                                        Correct.

                                        After rebooting my fiber modem, and releasing and renewing the WAN interface it is working again.

                                        To see if it has any affect, I also deleted the IPv6 Q9 DNS servers.

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          stephenw10 Netgate Administrator
                                          last edited by Feb 9, 2025, 6:57 PM

                                          Hmm, weird. Hard to imagine what could have caused that for pfSense but not clients behind it. 🤔

                                          E 1 Reply Last reply Feb 11, 2025, 11:09 AM Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.