Shows "Version 2.8.1 is available" but Update Settings says "Up to date" at 2.7.2

jbum

My pfSense received the notice that an upgrade was available a couple of months ago. I believe it was for version 2.8.1. At that time, when I navigated to the Update Settings screen, there was an upgrade/update button to starts the upgrade process. The upgrade started and after an hour or so I checked back and it appeared to have finished. I rebooted expected version 2.8.1 to show but it was still 2.7.2.

Since then I still get the "Version 2.8.1 is available" on the dashboard but when I click on the little cloud arrow icon to update, I see that the version is 2.7.2 with the "Up to date" status. I have tried most, if not all, of the suggestions including

switching the branch back and forth
refreshing the repository configuration and update script
bootstrapping pkg
forcing pkg metadata update
running certctl rehash
running a manual check for updates using pfSense-upgrade -d -c
forced pkg reinstall

At this point, I'm at a loss as to how to fix this. Worst case, I would just install the new version and try to restore the configuration from my backup file.

Any help would be appreciated.

stephenw10

It probably installed some pkgs from the upgrade but missed the meta pkg that the version check uses.

Try checking what is still available. Make sure the branch is set to 2.8.1 then run at the CLI: pkg-static upgrade See what packages are offered there.

jbum

@stephenw10 thanks for the reply.

This is what I see in the dashboard.

and on the system update view.

The pkg-static upgrade command gives me the following:

# pkg-static upgrade
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
Updating database digests format: 100%      1 B   0.0kB/s    00:01    
Checking for upgrades (1 candidates): 100%      1 B   0.0kB/s    00:01    
Processing candidates (1 candidates): 100%      1 B   0.0kB/s    00:01    
Checking integrity... done (0 conflicting)
Your packages are up to date.

I'm seeing 0% for the fetching status for meta.conf and packagesite.pkg. That seems a bit odd. Is that expected?

stephenw10

It's such a tiny file it only shows that. It's expected.

What does pkg info -x pfsense show?

jbum

@stephenw10

# pkg info -x pfSense
pfSense-2.7.2
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-2.7.2
pfSense-boot-2.7.2
pfSense-composer-deps-0.1
pfSense-default-config-2.7.2
pfSense-kernel-pfSense-2.7.2
pfSense-pkg-Avahi-2.2_4
pfSense-pkg-WireGuard-0.2.1
pfSense-pkg-haproxy-0.63_2
pfSense-pkg-pfBlockerNG-3.2.0_8
pfSense-pkg-snort-4.1.6_17
pfSense-pkg-sudo-0.3_8
pfSense-repo-2.7.2
pfSense-repoc-20230912
pfSense-upgrade-1.2.1
php82-pfSense-module-0.95

stephenw10

Ah, seems like it's not actually looking at the 2.8.1 repo then.

What does pkg -d update show?

jbum

@stephenw10

This is what I see.

# pkg -d update
DBG(1)[13338]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[13338]> PkgRepo: verifying update for pfSense-core
DBG(1)[13338]> PkgRepo: need forced update of pfSense-core
DBG(1)[13338]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[13338]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
DBG(1)[13338]> curl_open
DBG(1)[13338]> Fetch: fetcher used: pkg+https
DBG(1)[13338]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf

DBG(1)[13338]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.209:443...
* Connected to pkg01-atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/meta.conf HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:31:25 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 06 Dec 2023 21:23:58 GMT
< Connection: keep-alive
< ETag: "6570e66e-a3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
* Connection #0 to host pkg01-atx.netgate.com left intact
DBG(1)[13338]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg
DBG(1)[13338]> curl_open
DBG(1)[13338]> Fetch: fetcher used: pkg+https
DBG(1)[13338]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg

DBG(1)[13338]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x3b769b2318a0 [serially]
* Re-using existing connection with host pkg01-atx.netgate.com
> GET /pfSense_v2_7_2_amd64-core/packagesite.pkg HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:31:25 GMT
< Content-Type: application/octet-stream
< Content-Length: 1496
< Last-Modified: Wed, 06 Dec 2023 21:23:59 GMT
< Connection: keep-alive
< ETag: "6570e66f-5d8"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%    1 KiB   1.5kB/s    00:01    
* Connection #0 to host pkg01-atx.netgate.com left intact
DBG(1)[13338]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
DBG(1)[13610]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[13338]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-pfSense-core.sqlite'
Processing entries: 100%
pfSense-core repository update completed. 4 packages processed.
Updating pfSense repository catalogue...
DBG(1)[13338]> PkgRepo: verifying update for pfSense
DBG(1)[13338]> PkgRepo: need forced update of pfSense
DBG(1)[13338]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[13338]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf
DBG(1)[13338]> curl_open
DBG(1)[13338]> Fetch: fetcher used: pkg+https
DBG(1)[13338]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf

DBG(1)[13338]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.207:443...
* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:31:25 GMT
< Content-Type: application/octet-stream
< Content-Length: 179
< Last-Modified: Fri, 16 May 2025 16:29:21 GMT
< Connection: keep-alive
< ETag: "682767e1-b3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01    
* Connection #0 to host pkg00-atx.netgate.com left intact
DBG(1)[13338]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg
DBG(1)[13338]> curl_open
DBG(1)[13338]> Fetch: fetcher used: pkg+https
DBG(1)[13338]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg

DBG(1)[13338]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x3b769b312860 [serially]
* Re-using existing connection with host pkg00-atx.netgate.com
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:31:25 GMT
< Content-Type: application/octet-stream
< Content-Length: 196242
< Last-Modified: Fri, 16 May 2025 16:29:21 GMT
< Connection: keep-alive
< ETag: "682767e1-2fe92"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%  192 KiB 196.2kB/s    00:01    
* Connection #0 to host pkg00-atx.netgate.com left intact
DBG(1)[13338]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[16029]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[13338]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-pfSense.sqlite'
Processing entries: 100%
pfSense repository update completed. 550 packages processed.
All repositories are up to date.

stephenw10

Yup still pulling from 2.7.2. Go to System > Update > Update Settings and resave the branch at 2.8.1. See if that fixes it.

jbum

@stephenw10

Resaved the 2.8.1 branch

It still says "Up to date."

Output from "pkd -d update"

# pkg -d update
DBG(1)[21292]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[21292]> PkgRepo: verifying update for pfSense-core
DBG(1)[21292]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[21292]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
DBG(1)[21292]> curl_open
DBG(1)[21292]> Fetch: fetcher used: pkg+https
DBG(1)[21292]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf

DBG(1)[21292]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.209:443...
* Connected to pkg01-atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/meta.conf HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:45:49 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 06 Dec 2023 21:23:58 GMT
< Connection: keep-alive
< ETag: "6570e66e-a3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[21292]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg
DBG(1)[21292]> curl_open
DBG(1)[21292]> Fetch: fetcher used: pkg+https
DBG(1)[21292]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg

DBG(1)[21292]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg01-atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pkg01-atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/packagesite.pkg HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:45:49 GMT
< Content-Type: application/octet-stream
< Content-Length: 1496
< Last-Modified: Wed, 06 Dec 2023 21:23:59 GMT
< Connection: keep-alive
< ETag: "6570e66f-5d8"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[21292]> PkgRepo: verifying update for pfSense
DBG(1)[21292]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[21292]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf
DBG(1)[21292]> curl_open
DBG(1)[21292]> Fetch: fetcher used: pkg+https
DBG(1)[21292]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf

DBG(1)[21292]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.209:443...
* Connected to pkg01-atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Fri, 16 May 2025 16:29:21 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:45:49 GMT
< Content-Type: application/octet-stream
< Content-Length: 179
< Last-Modified: Fri, 16 May 2025 16:29:21 GMT
< Connection: keep-alive
< ETag: "682767e1-b3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[21292]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg
DBG(1)[21292]> curl_open
DBG(1)[21292]> Fetch: fetcher used: pkg+https
DBG(1)[21292]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg

DBG(1)[21292]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg01-atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pkg01-atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Apr 10 00:00:00 2025 GMT
*  expire date: May 11 23:59:59 2026 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Fri, 16 May 2025 16:29:21 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Fri, 12 Dec 2025 19:45:50 GMT
< Content-Type: application/octet-stream
< Content-Length: 196242
< Last-Modified: Fri, 16 May 2025 16:29:21 GMT
< Connection: keep-alive
< ETag: "682767e1-2fe92"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
< 
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

pfSense repository is up to date.
All repositories are up to date.

Can I manually update a file to force it to 2.8.1?

stephenw10

Possibly but you really shouldn't. Try: pfSense-repoc -NDJ

You shouldn't post the full output from that here since it includes device details. But make sure it's actually returning both pkg repo details.

jbum

@stephenw10
It's complaining about illegal options when I issue that command.

# pfSense-repoc -NDJ
pfSense-repoc: illegal option -- N
pfSense-repoc: dynamic repositories client
Options:
	-e		eligibility check - check for pfSense Plus eligibility
	-n		dry run - do not write any files
	-q		quiet mode - do not produce any output
	-t		text messages - print the text formatted messages (no HTML)
	-v		print the components version

stephenw10

Oh sorry N is a new option. Try: pfSense-repoc -DJ

jbum

@stephenw10
I was quite sure which part was device specific details or not. Hopefully, the pasted content below is sufficient.

# pfSense-repoc -DJ
OS: FreeBSD
OS Version: 14.0-CURRENT
Platform: amd64
Product: pfSense
Version: 2.7.2-RELEASE
FS type: zfs
Request query: {"platform":"unknown hardware","os":"FreeBSD","osver":"14.0-CURRENT","prod":"pfSense","ver":"2.7.2-RELEASE","ed":"Community","fstype":"zfs","pkgs":"[{\"name\":\"sudo\",\"ver\":\"0.3_8\"},{\"name\":\"Avahi\",\"ver\":\"2.2_4\"},{\"name\":\"snort\",\"ver\":\"4.1.6_17\"},{\"name\":\"haproxy\",\"ver\":\"0.63_2\"},{\"name\":\"WireGuard\",\"ver\":\"0.2.1\"},{\"name\":\"pfBlockerNG\",\"ver\":\"3.2.0_8\"}]"}
{
    "repos": {
        "repo": [
            {
                "abi": "FreeBSD:15:amd64",
                "altabi": "freebsd:15:x86:64",
                "conf": "< some hash >",
                "name": "2_8_1",
                "descr": "Current Stable Version (2.8.1)",
                "product": "pfSense Community Edition",
                "is_release": "yes",
                "osversion": null
            },
            {
                "abi": "FreeBSD:14:amd64",
                "altabi": "freebsd:14:x86:64",
                "conf": "< some hash >",
                "name": "2.7.2",
                "descr": "Previous Stable Version (2.7.2)",
                "default": "yes",
                "product": "pfSense Community Edition",
                "is_release": "no",
                "osversion": null
            }
        ]
    },
    . . . 
}

stephenw10

Hmm curious. Have you ever used any 3rd party repos for a specific pkg? Some of the instructions out there have you add an override file that can then prevent setting a branch.

What does ls -ls /usr/local/etc/pkg/repos show?

jbum

@stephenw10
I don't believe so. I have only installed software via the GUI and don't recall every adding custom repos.

# ls -ls /usr/local/etc/pkg/repos/
total 1
1 -rw-r--r--  1 root wheel 26 Dec  6  2023 FreeBSD.conf
1 lrwxr-xr-x  1 root wheel 56 Dec 12 11:44 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-2.7.2.conf

Also, I see

# cat /usr/local/etc/pkg/repos/FreeBSD.conf 
FreeBSD: { enabled: no  }
# ls /usr/local/etc/pfSense/pkg/repos/
pfSense-repo-2.7.2.abi		pfSense-repo-2_8_1.abi
pfSense-repo-2.7.2.altabi	pfSense-repo-2_8_1.altabi
pfSense-repo-2.7.2.conf		pfSense-repo-2_8_1.conf
pfSense-repo-2.7.2.default	pfSense-repo-2_8_1.descr
pfSense-repo-2.7.2.descr	pfSense-repo-2_8_1.name
pfSense-repo-2.7.2.name

Patch

@jbum said in Shows "Version 2.8.1 is available" but Update Settings says "Up to date" at 2.7.2:

This is what I see in the dashboard.
version.jpg

I just clicked on the download arrow on the summary page / dashboard when a similar thing happened for me some time ago. Update then proceeded as expected.

stephenw10

Hmm. when you select the 2.8.1 branch that symlink should be updated to point at it. You could probably do that manually though you really shouldn't have to.

jbum

@stephenw10
Given that I was ready to do a fresh install of 2.8.1, it's worth a try. I'll update you tomorrow when I find a good time to potentially take my internet access offline.

jbum

I changed that symlink to point to the 2.8.1 conf file but I noticed that the name of the target was "pfSense-repo-2_8_1.conf" with underscores and not "." for the version number. Not sure if that has any significance but it looked odd compared to the 2.7.2 version.

# ls -l
total 1
-rw-r--r--  1 root wheel 26 Dec  6  2023 FreeBSD.conf
lrwxr-xr-x  1 root wheel 56 Dec 14 04:20 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-2_8_1.conf

Anyway, after updating the reference, there was no change in the UI - still says 2.7.2 and up to date. I re-saved the branch version in update settings and that put the symlink back to 2.7.2.

# ls -l
total 1
-rw-r--r--  1 root wheel 26 Dec  6  2023 FreeBSD.conf
lrwxr-xr-x  1 root wheel 56 Dec 14 04:20 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-2.7.2.conf

stephenw10

Yup that's expected, the naming format was changed. You should see:

[2.7.2-RELEASE][admin@cedev-3.stevew.lan]/root: ls -ls /usr/local/etc/pfSense/pkg/repos/
total 14
1 -rw-r--r--  1 root wheel  16 Oct 28 18:55 pfSense-repo-2.7.2.abi
1 -rw-r--r--  1 root wheel  17 Oct 28 18:55 pfSense-repo-2.7.2.altabi
5 -rw-r--r--  1 root wheel 465 Oct 28 18:55 pfSense-repo-2.7.2.conf
1 -rw-r--r--  1 root wheel   1 Oct 28 18:55 pfSense-repo-2.7.2.default
1 -rw-r--r--  1 root wheel  31 Oct 28 18:55 pfSense-repo-2.7.2.descr
1 -rw-r--r--  1 root wheel   5 Oct 28 18:55 pfSense-repo-2.7.2.name
1 -rw-r--r--  1 root wheel  16 Oct 28 18:55 pfSense-repo-2_8_1.abi
1 -rw-r--r--  1 root wheel  17 Oct 28 18:55 pfSense-repo-2_8_1.altabi
5 -rw-r--r--  1 root wheel 465 Oct 28 18:55 pfSense-repo-2_8_1.conf
1 -rw-r--r--  1 root wheel  30 Oct 28 18:55 pfSense-repo-2_8_1.descr
1 -rw-r--r--  1 root wheel   5 Oct 28 18:55 pfSense-repo-2_8_1.name

[2.7.2-RELEASE][admin@cedev-3.stevew.lan]/root: ls -ls /usr/local/etc/pkg/repos/
total 1
1 -rw-r--r--  1 root wheel 26 Dec  6  2023 FreeBSD.conf
1 lrwxr-xr-x  1 root wheel 56 Oct 28 19:00 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-2_8_1.conf

When you change the firmware branch in the gui the config file should be updated with the line:
+ <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-2_8_1.conf</pkg_repo_conf_path>