Updater signature check failed

maverick_slo

@doktornotor:
Are you kidding me?
See attached image, server is correctly selected.

doktornotor

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).

maverick_slo

I did press save.

maverick_slo

I`ve read in your thread that something was broken…
Maybe that was the cause for my problem too :)

pfoo

Considering that updates.pfsense.org/ is currently down, they might be updating it for 2.1 release

monkfish

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!

maverick_slo

Huh not good…
I wanted to do the upgrades today but I guess will have to wait again :)

kejianshi

Update server is down… I kept pressing the update button over and over as doktornotor suggested then this happened.

deadmouse.jpg_thumb

doktornotor

R.I.P. :'( :P

kejianshi

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

maverick_slo

We are back in business :)

cmb

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

kejianshi

Works. :D

maverick_slo

Just upgraded.
Final reboot and thats it, let the dust begin doing its job on sitting on perfect firewall :)

Thanks to all involved!