2.7.2 Unable to check for update
-
Hmm. Do you have the update check disabled perhaps?
Do you see any available packages in the Package Manager?
-
-
Checked today, randomly working again.
-
Hmm, and you can see available pkgs now?
-
@stephenw10 yes sir.
-
Annnnd broke again
-
Hmm, that feels like some issue in the route.
As before though try running
pkg-static -d updateto see why it can't see packages. -
DBG(1)[24353]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[24353]> PkgRepo: verifying update for pfSense-core DBG(1)[24353]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[24353]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf DBG(1)[24353]> curl_open DBG(1)[24353]> Fetch: fetcher used: pkg+https DBG(1)[24353]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf DBG(1)[24353]> 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: Mar 28 00:00:00 2024 GMT * expire date: Apr 28 23:59:59 2025 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: < Server: nginx < Date: Thu, 12 Sep 2024 05:50:17 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)[24353]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg DBG(1)[24353]> curl_open DBG(1)[24353]> Fetch: fetcher used: pkg+https DBG(1)[24353]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg DBG(1)[24353]> 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: Mar 28 00:00:00 2024 GMT * expire date: Apr 28 23:59:59 2025 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: < Server: nginx < Date: Thu, 12 Sep 2024 05:50:17 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)[24353]> PkgRepo: verifying update for pfSense DBG(1)[24353]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite' DBG(1)[24353]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf DBG(1)[24353]> curl_open DBG(1)[24353]> Fetch: fetcher used: pkg+https DBG(1)[24353]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf DBG(1)[24353]> 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: Mar 28 00:00:00 2024 GMT * expire date: Apr 28 23:59:59 2025 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: Tue, 10 Sep 2024 16:51:58 GMT < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Thu, 12 Sep 2024 05:50:18 GMT < Content-Type: application/octet-stream < Content-Length: 178 < Last-Modified: Tue, 10 Sep 2024 16:51:58 GMT < Connection: keep-alive < ETag: "66e0792e-b2" < 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)[24353]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg DBG(1)[24353]> curl_open DBG(1)[24353]> Fetch: fetcher used: pkg+https DBG(1)[24353]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg DBG(1)[24353]> 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: Mar 28 00:00:00 2024 GMT * expire date: Apr 28 23:59:59 2025 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: Tue, 10 Sep 2024 16:51:58 GMT < HTTP/1.1 200 OK Fetching packagesite.pkg: < Server: nginx < Date: Thu, 12 Sep 2024 05:50:18 GMT < Content-Type: application/octet-stream < Content-Length: 160388 < Last-Modified: Tue, 10 Sep 2024 16:51:58 GMT < Connection: keep-alive < ETag: "66e0792e-27284" < 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. -
Hmm, that looks OK. I wouldn't expect any issues from that output.
Yet you are still seeing 'Unable to check for updates when it shows that?
-
@stephenw10 yes sir, I am.
-
What doe you see from the output of:
pfSense-upgrade -d? -
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. 550 packages processed.
All repositories are up to date.
Your packages are up to date
-
That's not the 'output' of this question :
@stephenw10 said in 2.7.2 Unable to check for update:
What doe you see from the output of: pfSense-upgrade -d ?
-
Indeed it should look like:
[2.7.2-RELEASE][admin@t70.stevew.lan]/root: pfSense-upgrade -d Messages: Your TAC Subscription expired on 2023-07-08 05:00:00. Please renew your TAC Subscription or purchase a pfSense+ subscription by visiting the <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a>. >>> 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. 550 packages processed. All repositories are up to date. Your packages are up to dateYou may or may not have a message in there. That test instance previously had a TAC subscription.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.