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

    pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    41 Posts 3 Posters 4.1k 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.
    • GertjanG
      Gertjan @yon 0
      last edited by

      @yon-0 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:

      @stephenw10

      pfsense-plus-pkg00.atx.netgate.com no support https

      It does - if 'https' was out on the server side, "millions" wouldn't be able to update/upgrade pfSense anymore. Didn't saw that announced on the forum 😊
      For me, the url resolved to the same IPs as you, IPv6 was chosen as it came first, and connected right away :

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

DBG(1)[77048]> 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 [2610:160:11:18::209]:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (2610:160:11:18::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-core/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.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, 07 May 2024 06:33:02 GMT
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-b2"
<
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[77048]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg
DBG(1)[77048]> curl_open
DBG(1)[77048]> Fetch: fetcher used: pkg+https
DBG(1)[77048]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg

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

      A wild guess : something doesn't work and while you were trying you got yourself blacklisted ?

      • SSL connection timeout

      Did you use/try the certificate rehash command ?

      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
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Try: pkg-static -d4 update

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

          @stephenw10
          Yeah, every time 2610:160:11:18::209 was used. And failed.
          Although, imho, "2610:160:11:18::209 port 443" was reached, but SSL negotiation failed.

          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
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by stephenw10

            Yup it looks like that. It's not showing a failed client cert though. Easy test to try IPv4 so might as well confirm it.

            yon 0Y 1 Reply Last reply Reply Quote 0
            • yon 0Y
              yon 0 @stephenw10
              last edited by

              @stephenw10

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

DBG(1)[90808]> 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-v23_09_1_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:16 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 2

* 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-v23_09_1_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:18 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 1

* 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
* 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-v23_09_1_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:19 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/meta.txz
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/meta.txz

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

* 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
* 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-v23_09_1_amd64-core/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:20 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 2

* 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
* 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-v23_09_1_amd64-core/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:21 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 1

* 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
* 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-v23_09_1_amd64-core/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:22 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.pkg
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.pkg

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

* 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
* 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-v23_09_1_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:23 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 2

* 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
* 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-v23_09_1_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:24 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 1

* 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
* 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-v23_09_1_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:25 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.txz
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.txz

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

* 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
* 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-v23_09_1_amd64-core/packagesite.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:27 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 2

* 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
* 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-v23_09_1_amd64-core/packagesite.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:28 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 1

* 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
* 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-v23_09_1_amd64-core/packagesite.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:29 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[90808]> PkgRepo: verifying update for pfSense
DBG(1)[90808]> PkgRepo: need forced update of pfSense
DBG(1)[90808]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf

DBG(1)[90808]> 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:30 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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...
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:32 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:33 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.txz
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.txz

DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:34 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:35 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:36 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
DBG(1)[90808]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg
DBG(1)[90808]> curl_open
DBG(1)[90808]> Fetch: fetcher used: pkg+https
DBG(1)[90808]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg

DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:37 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:38 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> CURL> attempting to fetch from , left retry 1


< HTTP/1.1 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:41 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
DBG(1)[90808]> 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
* 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-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.txz HTTP/1.1
Host: pfsense-plus-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 400 Bad Request
< Server: nginx
< Date: Tue, 07 May 2024 15:51:42 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
< 
* Closing connection
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!
              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ok so 'Bad Request' there implies an invalid client cert. A different error than your saw over IPv6. Which is interesting.

                So try first: pfSense-repoc then pkg-static -d4 update.

                yon 0Y 1 Reply Last reply Reply Quote 0
                • yon 0Y
                  yon 0 @stephenw10
                  last edited by

                  @stephenw10 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:

                  pkg-static -d4 update

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

DBG(1)[59015]> 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-v23_09_1_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-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: Tue, 07 May 2024 16:05:05 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 06 Dec 2023 23:08:54 GMT
< Connection: keep-alive
< ETag: "6570ff06-a3"
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[59015]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.pkg
DBG(1)[59015]> curl_open
DBG(1)[59015]> Fetch: fetcher used: pkg+https
DBG(1)[59015]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core/packagesite.pkg

DBG(1)[59015]> 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: 0x26df09c2b8d0 [serially]
* Re-using existing connection with host pfsense-plus-pkg00.atx.netgate.com
> GET /pfSense_plus-v23_09_1_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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: Tue, 07 May 2024 16:05:05 GMT
< Content-Type: application/octet-stream
< Content-Length: 1576
< Last-Modified: Wed, 06 Dec 2023 23:08:55 GMT
< Connection: keep-alive
< ETag: "6570ff07-628"
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%    2 KiB   1.6kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[59015]> PkgRepo: extracting packagesite.yaml of repo pfSense-core
DBG(1)[97591]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[59015]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-pfSense-core.sqlite'
Processing entries: 100%
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
DBG(1)[59015]> PkgRepo: verifying update for pfSense
DBG(1)[59015]> PkgRepo: need forced update of pfSense
DBG(1)[59015]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[59015]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf
DBG(1)[59015]> curl_open
DBG(1)[59015]> Fetch: fetcher used: pkg+https
DBG(1)[59015]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf

DBG(1)[59015]> 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-v23_09_1_amd64-pfSense_plus_v23_09_1/meta.conf HTTP/1.1
Host: pfsense-plus-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: Tue, 07 May 2024 16:05:07 GMT
< Content-Type: application/octet-stream
< Content-Length: 178
< Last-Modified: Mon, 29 Apr 2024 18:03:12 GMT
< Connection: keep-alive
< ETag: "662fe0e0-b2"
< Accept-Ranges: bytes
< 
Fetching meta.conf: 100%    178 B   0.2kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[59015]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg
DBG(1)[59015]> curl_open
DBG(1)[59015]> Fetch: fetcher used: pkg+https
DBG(1)[59015]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg

DBG(1)[59015]> 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: 0x26df09d0ed70 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1/packagesite.pkg HTTP/1.1
Host: pfsense-plus-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: Tue, 07 May 2024 16:05:08 GMT
< Content-Type: application/octet-stream
< Content-Length: 197252
< Last-Modified: Mon, 29 Apr 2024 18:03:12 GMT
< Connection: keep-alive
< ETag: "662fe0e0-30284"
< Accept-Ranges: bytes
< 
Fetching packagesite.pkg: 100%  193 KiB 197.3kB/s    00:01    
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[59015]> PkgRepo: extracting packagesite.yaml of repo pfSense
DBG(1)[98709]> PkgRepo: extracting signature of repo in a sandbox
DBG(1)[59015]> Pkgrepo, reading new packagesite.yaml for '/var/db/pkg/repo-pfSense.sqlite'
Processing entries: 100%
pfSense repository update completed. 739 packages processed.
All repositories are up to date.
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by stephenw10

                    Ok looks good. So you should be able to upgrade with: pfSense-upgrade -d4 after setting the repo branch to 24.03

                    yon 0Y 1 Reply Last reply Reply Quote 0
                    • yon 0Y
                      yon 0 @stephenw10
                      last edited by

                      @stephenw10

                      when steup 23.04, show

                      /root: pfSense-repoc
                      pfSense-repoc: no package 'name'
                      pfSense-repoc: no pfSense packages installed
                      [23.09.1-RELEASE]/root: pkg-static update
                      pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                      Updating pfSense-core repository catalogue...
                      pfSense-core repository is up to date.
                      Updating pfSense repository catalogue...
                      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

                        OK. What does pfSense-upgrade -d4 show?

                        yon 0Y 1 Reply Last reply Reply Quote 0
                        • yon 0Y
                          yon 0 @stephenw10
                          last edited by

                          @stephenw10

                          	pfSense-pkg-Filer-0.60.6_8 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pfSense-pkg-RRD_Summary-2.2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pfSense-pkg-Shellcmd-1.0.5_3 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pfSense-pkg-System_Patches-2.2.10_1 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pfSense-pkg-acme-0.8 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pfSense-pkg-sudo-0.3_8 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	pkcs11-helper-1.29.0 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	py311-libzfs-1.1.2023020700 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	py311-setuptools-63.1.0_1 [pfSense] (ABI changed: 'freebsd:14:*' -> 'freebsd:15:*')
	qstats-0.2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	radvd-2.19_2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	rate-0.9_2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	rrdtool-1.8.0_2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	rtrlib-0.8.0_1 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	scponly-4.8.20110526_5 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	smartmontools-7.4 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	ssh_tunnel_shell-0.2_1 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	uclcmd-0.2.20211204 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	voucher-0.1_3 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	vstr-1.0.15_1 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	whois-5.5.7 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	wol-0.7.1_4 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	wrapalixresetbutton-0.0.13 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	xinetd-2.3.15_2 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	zip-3.0_1 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')
	zstd-1.5.5 [pfSense] (ABI changed: 'freebsd:14:x86:64' -> 'freebsd:15:x86:64')

Number of packages to be removed: 52
Number of packages to be installed: 63
Number of packages to be upgraded: 54
Number of packages to be reinstalled: 97

The process will require 11 MiB more space.
337 MiB to be downloaded.
[1/214] Fetching duktape-lib-2.7.0.pkg: .......... done
[2/214] Fetching unbound-1.19.3.pkg: .......... done
[3/214] Fetching pfSense-pkg-Cron-0.3.8_4.pkg: . done
[4/214] Fetching wpa_supplicant-2.10_10.pkg: .......... done
[5/214] Fetching nginx-1.24.0_14,3.pkg: .......... done
[6/214] Fetching mpdecimal-2.5.1.pkg: ......... done
[7/214] Fetching filterlog-0.1_10.pkg: . done
[8/214] Fetching dpinger-3.3.pkg: . done
[9/214] Fetching php83-filter-8.3.1.pkg: . done
[10/214] Fetching libidn2-2.3.4.pkg: .......... done
[11/214] Fetching php83-pdo_sqlite-8.3.1.pkg: . done
[12/214] Fetching libuv-1.47.0.pkg: ........ done
[13/214] Fetching php83-pear-Net_URL2-2.2.1.pkg: . done
[14/214] Fetching bsnmp-ucd-0.4.5.pkg: .. done
[15/214] Fetching lzo2-2.10_1.pkg: ...... done
[16/214] Fetching php83-libbe-0.2.1.pkg: . done
[17/214] Fetching libunistring-1.1.pkg: .......... done
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            So it's upgrading correctly to 24.03?

                            yon 0Y 2 Replies Last reply Reply Quote 0
                            • yon 0Y
                              yon 0 @stephenw10
                              last edited by

                              @stephenw10

                              YES, upgrade to 24.03 now

                              Crash report begins.  Anonymous machine information:

amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #0 plus-RELENG_24_03-n256311-e71f834dd81: Fri Apr 19 00:28:14 UTC 2024     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/obj/amd64/Y4MAEJ2R/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/sources/FreeBS

Crash report details:

PHP Errors:
[08-May-2024 01:06:28 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:28 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:32 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:32 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:32 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:43 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:43 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:43 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:48 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:48 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:50 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:50 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:50 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:51 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:51 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:52 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:06:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:00 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:07 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:07 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:07 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:17 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:17 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:17 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:22 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:22 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:22 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:23 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:29 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:29 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:29 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:34 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:34 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:34 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:41 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:41 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:41 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:47 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:48 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:48 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:53 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:53 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:53 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:07:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:00 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:09 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:09 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:09 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:24 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:25 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:38 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:47 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:47 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:47 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:54 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:55 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:08:56 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:00 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:02 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:06 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:06 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:06 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0
[08-May-2024 01:09:11 Asia/Shanghai] PHP Fatal error:  Unable to start pfSense module in Unknown on line 0



No FreeBSD crash data found.
                              1 Reply Last reply Reply Quote 0
                              • yon 0Y
                                yon 0 @stephenw10
                                last edited by

                                @stephenw10

                                I have upgraded to version 24.03, but I cannot access the public network using ipv6, although I can see that the routing is correct using bgp. Maybe I have to go back to an older version.

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

                                  Most issues after upgrading are due to the State Interface binding change:
                                  https://docs.netgate.com/pfsense/en/latest/config/advanced-firewall-nat.html#firewall-state-policy

                                  Try changing that to floating. Especially if you're using any VTI IPSec tunnels.

                                  yon 0Y 1 Reply Last reply Reply Quote 0
                                  • yon 0Y
                                    yon 0 @stephenw10
                                    last edited by

                                    @stephenw10

                                    i using wireguard and openvpn for bgp. how i config it?

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

                                      Well first try just setting the global value back to floating. If that allows BGP to come up then look at where it was being blocked with interface bound states.

                                      yon 0Y 1 Reply Last reply Reply Quote 0
                                      • yon 0Y
                                        yon 0 @stephenw10
                                        last edited by

                                        @stephenw10 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:

                                        Well first try just setting the global value back to floating. If that allows BGP to come up then look at where it was being blocked with interface bound states.

                                        Where is this option?

                                        alt text

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

                                          It's Firewall State Policy which is in the advanced options section there but only in 24.03. That sreenshot is from 23.09.1

                                          yon 0Y 1 Reply Last reply Reply Quote 0
                                          • yon 0Y
                                            yon 0 @stephenw10
                                            last edited by yon 0

                                            @stephenw10

                                            System_ Advanced_ Firewall & NAT.jpg

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