PfSense servers faulty?

cyber7

OK, trying to upgrade/install packages I get errors of some meta files not existing. I then did a:

/root: pfSense-upgrade -4

and pfSense servers replied with this:

>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Internal Server Error
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Internal Server Error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Internal Server Error
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Internal Server Error
Unable to update repository pfSense

I then decided to have a look what is inside the "https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz" file by doing this:

curl -O https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz

and looking what is inside the file and got this:

 more meta.txz 

<title>500 Internal Server Error</title>

<center>

# 500 Internal Server Error

</center>

* * *

<center>nginx/1.11.3</center>

Telling me there is a problem within the pfSense update server environments… (500 Internal Error) - Even if I open the file from a browser I get the same thing...

Anyone from pfSense care to comment?

tib978

Same problem here.

2.3.2-RELEASE (amd64)
built on Tue Jul 19 12:44:43 CDT 2016
FreeBSD 10.3-RELEASE-p5

johnpoz

Not seeing that

if I download it and extract it I get these files

-rw-r–r-- 1 user user 246 Oct 6 14:00 meta
-rw-r--r-- 1 user user 451 Dec 31 1969 meta.pub
-rw-r--r-- 1 user user 256 Dec 31 1969 meta.sig
-rw-r--r-- 1 user user 4096 Oct 18 07:13 meta.tar

cat meta
version = 1;
packing_format = "txz";
digest_format = "sha256_base32";
digests = "digests";
manifests = "packagesite.yaml";
filesite = "filesite.yaml";
digests_archive = "digests";
manifests_archive = "packagesite";
filesite_archive = "filesite";

cat meta.pub
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtMIepBy6gBTdgTRg8SK/
7YSKM4C61PqkxEmmvAQx3XDtTLBnx0O3gr7EV+V/mMFYuFsEkBiUHDwL6ixxJeML
i+AipHR0ogvacc8LYKBBXWAT7QtvXs1v9pq7gDOUC9qxe2sZHQVXagh9ek9mJcjY
4cQEsfGlFvKCF4WWGxAxs2/5lJROOYMSe+I6W/m8GtAIpJQ8+FasFsX7BOM0kaDk
rd/YI5j+ANXJGJN6UUP5wQkh2i2tSZyVlvOwmhy6TyC/Eu22TDbrGiodBntEZLL3
dUURIkTU9/22LC6hy3VoVEimj5xOjIerrpCSmcbEUytZpExnAkDs9P6P5dh9QdFf
SwIDAQAB
-----END PUBLIC KEY-----

Looks ok to me.. Try it again.. They now and then do have issues yes.. Systems sometimes have problems ;)

AngelG

I had the same problem a few hours ago for a while. Now it works properly.