Updater signature check failed
-
Hi!
I tried to do auto update from:A new version is now available Current version: 2.1-RC2 Built On: Fri Sep 6 08:32:56 EDT 2013 New version: Wed Sep 11 18:16:50 EDT 2013 Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters/And I get:
There has been an error verifying the signature on this image. Update cannot continue. You can disable this check on the Updater Settings tab.Is it OK to skip signature check or should I wait?
Regards,
M
-
You should switch to the release branch. (And yeah, the snapshots have never been signed, required to disable it.)
-
Ummm I selected pfsense i386 stable updates from GUI and unchecked "Use a URL server for firmware upgrades other than www.pfsense.org".
Which URL should I use?
-
No, do NOT uncheck that box. Select the stable updates, leave that box checked and Save. Should point to http://updates.pfsense.org/_updaters, not the one you posted.
-
running 2.1-RC0 and switching "Default Auto Update URLs" to release branch is telling me that I am already on the latest version (which is false) .. Is there an upgrade process from 2.1-RC to 2.1-stable ?
-
Yup exactly the same problem that pfoo has…
Downloading new version information...done Obtaining current version information...done You are on the latest version.Server is now: http://updates.pfsense.org/_updaters
-
Did you really read my post above? The URLs are
http://updates.pfsense.org/_updaters (i386)
http://updates.pfsense.org/_updaters/amd64 (amd64)They will NOT get saved when you uncheck the checkbox after selecting stable from the dropdown.
-
Did you really read my post above? The URLs are
http://updates.pfsense.org/_updaters (i386)
http://updates.pfsense.org/_updaters/amd64 (amd64)They will NOT get saved when you uncheck the checkbox after selecting stable from the dropdown.
I am also getting this:
Downloading new version information…done
Obtaining current version information...doneYou are on the latest version.
My current version:
2.1-RC1 (i386)
built on Sat Aug 17 21:32:46 EDT 2013
FreeBSD 8.3-RELEASE-p9You are on the latest version.
-
@doktornotor:
Are you kidding me?
See attached image, server is correctly selected.
-
No, I'm not killing you. Just posting what worked here. Clearly the
Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters/
which you posted in the original post is not the proper one. No idea what trouble are you having now (provided you did actually click the Save button).
-
I did press save.
-
I`ve read in your thread that something was broken…
Maybe that was the cause for my problem too :)
-
Considering that updates.pfsense.org/ is currently down, they might be updating it for 2.1 release
-
Well the UK mirror updates are showing proper 2.1 firmware.
http://files.uk.pfsense.org/mirror/updates/
Two of my boxes were showing exact same symptoms - when set properly to "stable release" they were incorrectly stating I was on the latest version even though I had not updated.
If you're wanting to update may I suggest downloading the updates to your local computer and doing a manual update from file?
Alternatively, download the firmware direct to your pfsense machine, login to the console and select "13" update from console.
Both the above worked for me. Thanks to the developers and all involved for pfsense!
-
Huh not good…
I wanted to do the upgrades today but I guess will have to wait again :)
-
Update server is down… I kept pressing the update button over and over as doktornotor suggested then this happened.
-
R.I.P. :'( :P
-
Going to the auto-updater settings when the server is down locks out the webgui - not even a Restart webConfigurator fixes it. Had to reboot…
So, incase anyone else is as curious as me don't do that :P
-
We are back in business :)
-
Yeah it's been available again for a bit. Had to remove public access to updates.pfsense.org to fix something, which was quick, but my current release testing setup isn't quick when you go through every single size and platform, and have all those test VMs running on your laptop. The testing setup will be on real servers well before the next release so if we have to do something like that, it won't take hours of waiting. I also did some things to prevent that from happening again.
Sorry for the inconvenience, knock yourselves out upgrading now. ;D
-
Works. :D
-
Just upgraded.
Final reboot and thats it, let the dust begin doing its job on sitting on perfect firewall :)Thanks to all involved!
