pfSense Unable to check for updates & WebUI Slow - 400 Bad Request

rtorres

Hello all,

I logged into my pfSense 24.03 box and noticed that the 'Netgate Services and Support' widget kept displaying a 'Retrieving support information' and never loaded.

I checked System -> Update and, after quite some time loading, I would see 'Could not connect to Netgate servers. Please try again later.' besides Messages.

I ran pkg-static update and I see a lot of errors occured:

Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!

Here's with the -d variable (removed some entries due to too many characters for a post):

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

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

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

< HTTP/1.1 400 Bad Request
< Server: nginx
< Date: Tue, 30 Apr 2024 04:39:24 GMT
< Content-Type: text/html
< Content-Length: 208
< Connection: close
<
* Closing connection

DBG(1)[71322]> 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: Tue, 30 Apr 2024 04:39:31 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!

Proxmox had a big recent update, not too sure if that had anything to do with pfSense - possible NDI deactivation?

Thank you for the help!

SamJWard

@rtorres Their site is currently down. However, it appears many staff members have no clue that they've been down all day. Not good.

rtorres

@SamJWard Thank you! Appreciate the reply.

I did make some changes to the DNS Resolver and though it was user error.

tstockman

Hmmmmm...there went a whole heap of time today chasing shadows on a day where i didn't have time to be doing that!! :/

Darkk

@SamJWard Hmm... they don't have monitoring system in place to notify their server admins that the systems are down? Would be nice if they have a network status page on the netgate support site in cases like this so we don't waste time trying to figure out if there is something wrong with our pfsense / netgate appliances like I dealt with today. This would also prevent un-necessary tickets.

Yes I am a bit frustrated to spend couple of hours troubleshooting only to find out it wasn't my instance. Although I am used to it in the IT world.

Least now I know after finding a couple of posts about this that I can stop troubleshooting and wait till in the morning to try again.