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

    check_upgrade (1): unknown error @ 2024-06-07 09:26:39

    Scheduled Pinned Locked Moved General pfSense Questions
    30 Posts 8 Posters 1.6k Views
    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

      SSH is not enabled by default. You have to enable it in System > Advanced > Admin Access.

      TAC57T 1 Reply Last reply Reply Quote 0
      • TAC57T
        TAC57 @stephenw10
        last edited by

        @stephenw10
        /root: pkg -d update
        DBG(1)[97448]> pkg initialized
        Updating pfSense-core repository catalogue...
        DBG(1)[97448]> PkgRepo: verifying update for pfSense-core
        DBG(1)[97448]> PkgRepo: need forced update of pfSense-core
        DBG(1)[97448]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
        DBG(1)[97448]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf
        DBG(1)[97448]> curl_open
        DBG(1)[97448]> Fetch: fetcher used: pkg+https
        DBG(1)[97448]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf

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

        • Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
        • Trying 208.123.73.209:443...
        • Trying [2610:160:11:18::209]:443...
        • Immediate connect fail for 2610:160:11:18::209: No route to host
        • ipv4 connect timeout after 29790ms, move on!
        • Failed to connect to pfsense-plus-pkg01.atx.netgate.com port 443 after 30020 ms: Timeout was reached
        • Closing connection
          DBG(1)[97448]> CURL> attempting to fetch from , left retry 2
        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          So it tries to use IPv6 and fails. It should then try IPv4 after that, does it not?

          You can force it to use v4 only with: pkg -d4 update

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

            Oh looks like that just times out. Does it have a valid route? Can you ping 208.123.73.209?

            TAC57T 1 Reply Last reply Reply Quote 0
            • TAC57T
              TAC57 @stephenw10
              last edited by

              @stephenw10
              C:\Users\Tom>ping 208.123.73.209

              Pinging 208.123.73.209 with 32 bytes of data:
              Reply from 208.123.73.209: bytes=32 time=39ms TTL=51
              Reply from 208.123.73.209: bytes=32 time=39ms TTL=51
              Reply from 208.123.73.209: bytes=32 time=39ms TTL=51
              Reply from 208.123.73.209: bytes=32 time=39ms TTL=51

              Ping statistics for 208.123.73.209:
              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
              Approximate round trip times in milli-seconds:
              Minimum = 39ms, Maximum = 39ms, Average = 39ms

              /root: pkg -d4 update
              DBG(1)[77568]> pkg initialized
              Updating pfSense-core repository catalogue...
              DBG(1)[77568]> PkgRepo: verifying update for pfSense-core
              DBG(1)[77568]> PkgRepo: need forced update of pfSense-core
              DBG(1)[77568]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
              DBG(1)[77568]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf
              DBG(1)[77568]> curl_open
              DBG(1)[77568]> Fetch: fetcher used: pkg+https
              DBG(1)[77568]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf

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

              • Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults

              • Trying 208.123.73.209:443...

              • ipv4 connect timeout after 29980ms, move on!

              • Failed to connect to pfsense-plus-pkg01.atx.netgate.com port 443 after 30039 ms: Timeout was reached

              • Closing connection
                DBG(1)[77568]> CURL> attempting to fetch from , left retry 2

              • Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults

              • Trying 208.123.73.207:443...

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

                But can you ping it from pfSense?

                TAC57T 1 Reply Last reply Reply Quote 0
                • TAC57T
                  TAC57 @stephenw10
                  last edited by

                  @stephenw10
                  [24.03-RELEASE][admin@pfsense.crites.local]/root: ping 208.123.73.209
                  PING 208.123.73.209 (208.123.73.209): 56 data bytes
                  64 bytes from 208.123.73.209: icmp_seq=0 ttl=54 time=443.919 ms
                  64 bytes from 208.123.73.209: icmp_seq=1 ttl=54 time=443.295 ms
                  64 bytes from 208.123.73.209: icmp_seq=2 ttl=54 time=443.034 ms
                  64 bytes from 208.123.73.209: icmp_seq=3 ttl=54 time=443.090 ms
                  64 bytes from 208.123.73.209: icmp_seq=4 ttl=54 time=443.255 ms
                  64 bytes from 208.123.73.209: icmp_seq=5 ttl=54 time=443.636 ms
                  64 bytes from 208.123.73.209: icmp_seq=6 ttl=54 time=443.890 ms

                  1 Reply Last reply Reply Quote 0
                  • TAC57T
                    TAC57 @stephenw10
                    last edited by TAC57

                    @stephenw10 Hey Steve, I've gotten pfBlockerNG running and for some reason package manager is now listing the available packages just fine!

                    Thanks,
                    -TAC

                    p.s. I can also get into pfSense just fine with winSCP.

                    1 Reply Last reply Reply Quote 2
                    • W
                      wheelhouse20 @TAC57
                      last edited by

                      @TAC57 could it be that you had pfsense plus which has now ran out.

                      1 Reply Last reply Reply Quote 0
                      • D
                        DominikHoffmann @stephenw10
                        last edited by

                        @stephenw10 said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                        Try running: pkg -d update to more error output.

                        My output is this

                        [24.03-RELEASE][admin@***.***.***.***]/root: pkg -d update
DBG(1)[46125]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[46125]> PkgRepo: verifying update for pfSense-core
DBG(1)[46125]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db'
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/meta.conf
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/meta.conf

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Host pfsense-plus-pkg01.atx.netgate.com:443 was resolved.
* IPv6: 2610:160:11:18::209
* IPv4: 208.123.73.209
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 02 Jul 2024 17:57:31 GMT
< Last-Modified: Fri, 19 Apr 2024 01:23:56 GMT
< Connection: keep-alive
< ETag: "6621c7ac-b2"
< 
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/data.pkg
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/data.pkg

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x5e069d61f870 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v24_03_aarch64-core/data.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> CURL> attempting to fetch from , left retry 2

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
* Host pfsense-plus-pkg00.atx.netgate.com:443 was resolved.
* IPv6: 2610:160:11:18::207
* IPv4: 208.123.73.207
*   Trying 208.123.73.207:443...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg00.atx.netgate.com
*  start date: Mar 15 20:23:11 2022 GMT
*  expire date: Feb 19 20:23:11 2122 GMT
*  common name: pfsense-plus-pkg00.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/data.pkg HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> CURL> attempting to fetch from , left retry 1

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Hostname pfsense-plus-pkg01.atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/data.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/data.txz
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/data.txz

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Hostname pfsense-plus-pkg01.atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/data.txz HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> CURL> attempting to fetch from , left retry 2

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
* Hostname pfsense-plus-pkg00.atx.netgate.com was found in DNS cache
*   Trying 208.123.73.207:443...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg00.atx.netgate.com
*  start date: Mar 15 20:23:11 2022 GMT
*  expire date: Feb 19 20:23:11 2122 GMT
*  common name: pfsense-plus-pkg00.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/data.txz HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> CURL> attempting to fetch from , left retry 1

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Hostname pfsense-plus-pkg01.atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/data.txz HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 404 Not Found
* Failure writing output to destination, passed 24 returned 23
* Closing connection
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/packagesite.pkg
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-core/packagesite.pkg

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Hostname pfsense-plus-pkg01.atx.netgate.com was found in DNS cache
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:23:56 GMT

* Request completely sent off
< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 02 Jul 2024 17:57:32 GMT
< Last-Modified: Fri, 19 Apr 2024 01:23:56 GMT
< Connection: keep-alive
< ETag: "6621c7ac-620"
< 
* Connection #6 to host pfsense-plus-pkg01.atx.netgate.com left intact
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[46125]> PkgRepo: verifying update for pfSense
DBG(1)[46125]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db'
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/meta.conf
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/meta.conf

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Host pfsense-plus-pkg01.atx.netgate.com:443 was resolved.
* IPv6: 2610:160:11:18::209
* IPv4: 208.123.73.209
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/1.x
> GET /pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Mon, 01 Jul 2024 19:18:28 GMT

* Request completely sent off
< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 02 Jul 2024 17:57:33 GMT
< Last-Modified: Mon, 01 Jul 2024 19:18:28 GMT
< Connection: keep-alive
< ETag: "66830104-b2"
< 
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[46125]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/data.pkg
DBG(1)[46125]> curl_open
DBG(1)[46125]> Fetch: fetcher used: pkg+https
DBG(1)[46125]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/data.pkg

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x5e069d712cb0 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v24_03_aarch64-pfSense_plus_v24_03/data.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.21.3
Accept: */*
If-Modified-Since: Mon, 01 Jul 2024 19:18:28 GMT

* Request completely sent off
< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 02 Jul 2024 17:57:33 GMT
< Last-Modified: Mon, 01 Jul 2024 19:18:28 GMT
< Connection: keep-alive
< ETag: "66830104-2de10"
< 
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
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

                          What are you upgrading from?

                          D 1 Reply Last reply Reply Quote 0
                          • D
                            DominikHoffmann @stephenw10
                            last edited by

                            @stephenw10 said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                            What are you upgrading from?

                            Not from anything specific. I just get that same notification that caused @TAC57 to start this thread:

                            Screenshot 2024-07-02 at 1.54.03 PM.png

                            “check_upgrade (1): unknown error”

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

                              @DominikHoffmann said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                              Not from anything specific.

                              So you've tried upgrading from multiple pfSense versions?

                              D 1 Reply Last reply Reply Quote 0
                              • D
                                DominikHoffmann @stephenw10
                                last edited by

                                @stephenw10: I am no upgrading at all.

                                I am wondering, whether this is something that the pkg_check.php script authored by @luckman212 generates that.

                                GertjanG 1 Reply Last reply Reply Quote 0
                                • GertjanG
                                  Gertjan @DominikHoffmann
                                  last edited by Gertjan

                                  @DominikHoffmann

                                  Noop.
                                  That script doesn't generate of modifies any files. It calls the same php pfSense function 'get_system_pkg_versio()' as the widget on the dashboard.
                                  And it uses the shell command "/usr/sbin/pkg upgrade -n ..." to enumerate the newer avaible packages, if any exists.
                                  It doesn't actually change anything.

                                  I'm using it every day, for years now.
                                  I have a x86 based 4100 with 24.03.

                                  edit :

                                  pkg -d update

                                  produces a lot of details, but no errors.

                                  The script file :

                                  [24.03-RELEASE][root@pfSense.bhf.tld]/root: php -q ./pkg_check.php
pfSense version 24.03_1 (installed) is current

                                  No "help me" PM's please. Use the forum, the community will thank you.
                                  Edit : and where are the logs ??

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

                                    Ah nice I didn't think it knew about the recent changes yet. But maybe it doesn't have to.

                                    1 Reply Last reply Reply Quote 0
                                    • K
                                      KB8DOA
                                      last edited by

                                      I am having the same problem with a Netgate 5100:

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

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

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.207:443...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg00.atx.netgate.com
*  start date: Mar 15 20:23:11 2022 GMT
*  expire date: Feb 19 20:23:11 2122 GMT
*  common name: pfsense-plus-pkg00.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:25:58 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-b2"
<
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg

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

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x170e7082f7e0 [serially]
* Re-using existing connection with host pfsense-plus-pkg00.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:25:58 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-62c"
<
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[55001]> PkgRepo: verifying update for pfSense
DBG(1)[55001]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Wed, 21 Aug 2024 15:44:04 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Wed, 21 Aug 2024 15:44:04 GMT
< Connection: keep-alive
< ETag: "66c60b44-b2"
<
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x170e70917ce0 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Wed, 21 Aug 2024 15:44:04 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Wed, 21 Aug 2024 15:44:04 GMT
< Connection: keep-alive
< ETag: "66c60b44-2ff4c"
<
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
pfSense repository is up to date.
All repositories are up to date.
                                      GertjanG 1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        What problem? That output shows a normal pkg update check.

                                        tinfoilmattT 1 Reply Last reply Reply Quote 0
                                        • tinfoilmattT
                                          tinfoilmatt @stephenw10
                                          last edited by

                                          @stephenw10 said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                                          What problem? That output shows a normal pkg update check.

                                          @KB8DOA, with debug output enabled (i.e. pkg -d update). a more 'normalized' level output:

                                          Updating pfSense-core repository catalogue...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
pfSense repository is up to date.
All repositories are up to date.

                                          or just run pkg update without the -d flag.

                                          1 Reply Last reply Reply Quote 0
                                          • GertjanG
                                            Gertjan @KB8DOA
                                            last edited by

                                            @KB8DOA

                                            Don't worry, I somewhat understand what you mean.
                                            This :

                                            70ce2722-8f49-497a-8cfe-2bea647df2d8-image.png

                                            looks alarming because it contain a negation (or something like that, I'm not native ...)
                                            Or, it's just an awkward notification.

                                            No "help me" PM's please. Use the forum, the community will thank you.
                                            Edit : and where are the logs ??

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.