OPNsense Forum

Archive => 21.1 Legacy Series => Topic started by: jwketchum on February 12, 2021, 08:12:55 PM

Title: Failed, no signature found
Post by: jwketchum on February 12, 2021, 08:12:55 PM
I am trying to upgrade from  20.7.8_4-amd64 to 21.1 through the web gui interface. I have repeatedly gotten the following response:
***GOT REQUEST TO UPGRADE: maj***
Fetching packages-21.1-OpenSSL-amd64.tar: .............................. failed, no signature found
***DONE***
I tried this with the source set to LeaseWeb in DC and NYC*BUG, with the same result.

CPU: Intel(R) Atom(TM) CPU E3845 @ 1.91GHz (4 cores)

Suggestions?

Thank you.
Title: Re: Failed, no signature found
Post by: franco on February 13, 2021, 09:46:13 PM
File downloads fine, check your proxies:

http://mirrors.nycbug.org/pub/opnsense/FreeBSD%3a12%3aamd64/20.7/sets/packages-21.1-OpenSSL-amd64.tar.sig


Cheers,
Franco
Title: Re: Failed, no signature found
Post by: jwketchum on February 14, 2021, 04:26:49 PM
Thanks for your reply, Franco.  But being a newcomer here, I need a bit more instruction.  I have successfully downloaded an install file from the DC mirror with no problems.  However, I don't want to do a fresh install, I want to upgrade my current installation to 21.1.  I haven't had a problem in the past updating the 20.7 release to the terminal update 20.7.8_4.  What do I need to do differently here?
Title: Re: Failed, no signature found
Post by: jwketchum on February 16, 2021, 04:31:06 PM
This problem resolved itself -- I was able, yesterday, to upgrade to 21.1, then update to 21.1.1.  I only made one change to the configuration prior to doing the upgrade, which was to set the Firewall>Settings>Advanced Disable force gateway option.  I did this to address an issue with lots of "dhcp6c transmit failed: No route to host" messages, which had the desired effect.  I have no idea whether this has anything to do with inability to properly download the upgrade files.