pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed
-
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 -
So it's upgrading correctly to 24.03?
-
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. -
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.
-
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-policyTry changing that to floating. Especially if you're using any VTI IPSec tunnels.
-
i using wireguard and openvpn for bgp. how i config it?
-
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.
-
@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?
-
It's
Firewall State Policywhich is in the advanced options section there but only in 24.03. That sreenshot is from 23.09.1 -
-
-
again happen:
pkg-static -d4 update
DBG(1)[98836]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[98836]> PkgRepo: verifying update for pfSense-core
DBG(1)[98836]> PkgRepo: need forced update of pfSense-core
DBG(1)[98836]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[98836]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf
DBG(1)[98836]> curl_open
DBG(1)[98836]> Fetch: fetcher used: pkg+https
DBG(1)[98836]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.confDBG(1)[98836]> 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 timeout
-
Closing connection
DBG(1)[98836]> 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 timeout
-
Closing connection
DBG(1)[98836]> CURL> attempting to fetch from , left retry 1 -
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 timeout
-
Closing connection
pkg-static: An error occured while fetching package
DBG(1)[98836]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.txz
DBG(1)[98836]> curl_open
DBG(1)[98836]> Fetch: fetcher used: pkg+https
DBG(1)[98836]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.txz
DBG(1)[98836]> CURL> attempting to fetch from , left retry 3
-
-
@yon-0 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:
SSL connection timeout
DNS looks fine.
It connects.
Looks like the Netgate packet server is doing some maintenance / isn't available right now.right now, for me,
pkg-static -d4 updateworks fine.
-
@Gertjan said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:
pkg-static -d4 update
just now..
pkg-static -d4 update DBG(1)[89282]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[89282]> PkgRepo: verifying update for pfSense-core DBG(1)[89282]> PkgRepo: need forced update of pfSense-core DBG(1)[89282]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[89282]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf DBG(1)[89282]> curl_open DBG(1)[89282]> Fetch: fetcher used: pkg+https DBG(1)[89282]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf DBG(1)[89282]> 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 timeout * Closing connection DBG(1)[89282]> CURL> attempting to fetch from , left retry 2 -
Are you using a proxy?
-
@stephenw10 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:
Are you using a proxy?
no, pfsense has install wiregaurd and openvpn .
-
whatt's for this ?
Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
-
That's expected, that file isn't present. The only error you're seeing is
SSL connection timeout. But it is able to connect to the server.That implies something in the route is preventing that connection. Thus I asked if you are connecting through a proxy.
Potentially it could be an MTU issue. I can ping that at a maximum payload size of 1464 for example:
[24.03-RELEASE][admin@cedev-3.stevew.lan]/root: ping -s 1464 pfsense-plus-pkg01.atx.netgate.com PING pfsense-plus-pkg01.atx.netgate.com (208.123.73.209): 1464 data bytes 1472 bytes from 208.123.73.209: icmp_seq=0 ttl=45 time=126.474 ms 1472 bytes from 208.123.73.209: icmp_seq=1 ttl=45 time=126.362 ms ^C --- pfsense-plus-pkg01.atx.netgate.com ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 126.362/126.418/126.474/0.056 ms -
@stephenw10 said in pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed:
ping -s 1464 pfsense-plus-pkg01.atx.netgate.com
ok , i changed mss to 1280. it can get ping.
just now
pkg-static -d4 update DBG(1)[29153]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[29153]> PkgRepo: verifying update for pfSense-core DBG(1)[29153]> PkgRepo: need forced update of pfSense-core DBG(1)[29153]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/meta.conf DBG(1)[29153]> 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-core/meta.conf HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:19 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-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: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:20 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-core/meta.txz HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:26 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)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg DBG(1)[29153]> 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-v24_03_amd64-core/packagesite.pkg HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:27 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-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: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:29 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-core/packagesite.pkg HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:30 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection pkg-static: An error occured while fetching package DBG(1)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.txz DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.txz DBG(1)[29153]> 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-v24_03_amd64-core/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:31 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-core/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:32 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-core/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:34 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)[29153]> PkgRepo: verifying update for pfSense DBG(1)[29153]> PkgRepo: need forced update of pfSense DBG(1)[29153]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite' DBG(1)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf DBG(1)[29153]> 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-pfSense_plus_v24_03/meta.conf HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:35 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-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: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:36 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/meta.conf HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:37 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection pkg-static: An error occured while fetching package DBG(1)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.txz DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.txz DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/meta.txz HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:39 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/meta.txz HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:40 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/meta.txz HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:41 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)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:42 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-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: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:44 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:45 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection pkg-static: An error occured while fetching package DBG(1)[29153]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz DBG(1)[29153]> curl_open DBG(1)[29153]> Fetch: fetcher used: pkg+https DBG(1)[29153]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:46 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg01.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:47 GMT < Content-Type: text/html < Content-Length: 208 < Connection: close < * Closing connection DBG(1)[29153]> 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-v24_03_amd64-pfSense_plus_v24_03/packagesite.txz HTTP/1.1 Host: pfsense-plus-pkg00.atx.netgate.com User-Agent: pkg/1.20.9 Accept: */* If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT < HTTP/1.1 400 Bad Request < Server: nginx < Date: Thu, 17 Oct 2024 14:53:49 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! -
OK run
pfSense-repoc -Nthen retry.The Bad Request error implies your client isn't sending a valid client cert. It probably needs to be updated since it couldn't connect until now.
