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

    2.7.2 Unable to check for update

    Scheduled Pinned Locked Moved
    Problems Installing or Upgrading pfSense Software
    3
    31
    1.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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, well that all looks good. It's still showing unable to check for updates?

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

        @stephenw10

        Yes sir. Maybe it’s PfBlocker or Suricata?

        But then again, if it was really blocked, option 13 at the front end shouldn’t work.

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

          There's no difference between that traffic from the CLI pkg check and what the GUI runs.

          Try: pfSense-upgrade -Uc
          That's what is actually run by the GUI.

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

            @stephenw10 said in 2.7.2 Unable to check for update:

            pfSense-upgrade -Uc

            [2.7.2-RELEASE][admin@pfSense.localdomain]/root: pfSense-upgrade -Uc
            Your system is up to date

            e3eda360-34aa-4971-b543-0724697a94a0-image.png

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

              Bizarre. Shouldn't matter but are you logged in as admin, or an admin user?

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

                @stephenw10 I never setup users nor have I had this issue over the years I’ve used pfsense. Bad install?

                Thanks for all the responses.

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

                  So that is when logged in as admin?

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

                    @stephenw10 sorry for the lack of clarity, yes, and SSH was root.

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

                      Hmm. Do you have the update check disabled perhaps?

                      Do you see any available packages in the Package Manager?

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

                        @stephenw10

                        68ea564b-8ad4-4259-a96f-e13fdae90ca8-image.jpeg

                        45521ce7-9b32-4888-8860-1e931302ed0a-image.png

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

                          Screenshot 2024-05-27 at 2.30.54 PM.png

                          Checked today, randomly working again.

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

                            Hmm, and you can see available pkgs now?

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

                              @stephenw10 yes sir.

                              M 1 Reply Last reply Reply Quote 1
                              • M
                                MxcZXAKM @MxcZXAKM
                                last edited by

                                @MxcZXAKM 175aa157-91b0-448c-aa8a-12e30ee78244-image.jpeg

                                Annnnd broke again

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

                                  Hmm, that feels like some issue in the route.

                                  As before though try running pkg-static -d update to see why it can't see packages.

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

                                    @stephenw10

                                    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.
                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      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?

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

                                        @stephenw10 yes sir, I am.

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

                                          What doe you see from the output of: pfSense-upgrade -d ?

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

                                            @stephenw10

                                            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

                                            IMG_0059.jpeg

                                            GertjanG 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post