opnsense-revert for unbound issue "failed"

[iguy]

I'm attempting to revert the unbound back to version 20.7.6 and it doesn't appear to work for me.  This is a new install into a VMware image from the 20.7 ISO file then updated to 20.7.7 immediately afterwards.   I log in via SSH or the console then hit 8 to go to shell. 

Then when I run

Code: [Select]

opnsense-revert -r 20.7.6 unbound I get the following:

Code: [Select]

root@opnsense:~ # opnsense-revert -r 20.7.6 unbound
Fetching unbound.txz: ............................... failed

if I run

Code: [Select]

curl -o unbound.txz http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD%3A12%3Aamd64/20.7/MINT/20.7.6/OpenSSL/Latest/unbound.txz
it takes about 10 seconds and it's done.   

What do I need to look at to figure out what's going on here?   

[deeler]

try 20.7 first

[MBfromOK]

Just another OPNSense user here... Any reason why you don't want to just patch up to the newest version - Created by unbound to address this issue?

Here is the command: pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

Per Franco: This patch is minimal

I was able to upgrade without rebooting the server, although I had to hard shutdown the server after the "broke" version installed to get my system to respond to commands via WebGUI or VM shell. 

[iguy]

I did the update command:  pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

It took about 10 mins to execute, something strange is going on here.   Everything else outside this instance is near instant response.   Things to do the pkg or other update checking is slow.  for example, checking for updates or plugin updates.   

Any ideas?   

[MBfromOK]

That was my experience as well after the upgrade, in my case the hard shutdown and reboot fixed the majority of my issues.

I saw this in the post discussing unbound issues:

Please check the interfaces it is listening to. Maybe there is something wrong. Change this setting and hit save. Then change it back and save again.

I have had issues in the past with the WAN connection losing its place and refusing to get a new IP (I am on a dynamic IP service) and swapping the interfaces (or setting the WAN the same interface as the LAN long enough to save, refresh the page and then swap back) fixed those issues.