OPNsense Forum
Archive => 18.7 Legacy Series => Topic started by: bonusmalus on September 19, 2018, 10:51:05 pm
-
Hi folks,
i have a problem here. I can not upgrade my system to v. 18.7.3 over the Webinterface (Firefox or Edge, no mater) i got every time the error message -> The package manager is not responding
(http://)
I have installed the new version 18.7.3 over console, but over the Webinterface is still showing v. 18.7.2 on the Update page
What can i do to fix this? I have already checked the Forum here for this Issue, the hint -> Prefer IPv4 over IPv6 was NOT the solution for me.
THX for any hint on this
-
Hi there,
Try different mirrors in near you in the settings. After debugging sessions in IRC it seemed that some ISPs don't like to access our default mirror's network for one reason or another and just hang while fetching.
Cheers,
Franco
-
Hi Franco,
your suggestion was the first thing I have tyred before my post.
Also changed from prod to dev and was the same.
cheers
Niko
-
Something is blocking your connectivity. Try to run this from the console and let us know the output to troubleshoot:
# sh -x /usr/local/opnsense/scripts/firmware/changelog.sh fetch
Cheers,
Franco
-
Also, make sure under System > General you have DNS servers such as 1.1.1.1 or 8.8.8.8
-
Looks like the update to .3 does this. Mine worked first thing today and took me to 18.7.3 and now the getting mirror times out all the time. I've tried a few mirrors now and I've tried the perfer IPc4 thing.
I don't have a clue if my IPv6 is working or not. I know on the providers kit IPv6 is not supported and there does not seem to be a way to turn this off within opnsense.
-
Set the interfaces->WAN IPv6 Configuration Type to None
Set the interfaces->LAN IPv6 Configuration Type to None
No IPv6
-
Something is blocking your connectivity. Try to run this from the console and let us know the output to troubleshoot:
# sh -x /usr/local/opnsense/scripts/firmware/changelog.sh fetch
Cheers,
Franco
@ Franco,
here is the output
+ set -e
+ DESTDIR=/usr/local/opnsense/changelog
+ WORKDIR=/tmp/changelog
+ FETCH='fetch -qT 5'
+ COMMAND=fetch
+ VERSION=''
+ [ fetch '=' fetch ]
+ changelog_fetch
+ cat /usr/local/opnsense/version/opnsense.abi
+ CORE_ABI=18.7
+ opnsense-verify -a
+ SYS_ABI=FreeBSD:11:amd64
+ URL=https://pkg.opnsense.org/FreeBSD:11:amd64/18.7/sets/changelog.txz
+ rm -rf /tmp/changelog
+ mkdir -p /tmp/changelog
+ fetch -qT 5 -o /tmp/changelog/changelog.txz.sig https://pkg.opnsense.org/FreeB SD:11:amd64/18.7/sets/changelog.txz.sig
fetch: transfer timed out
fetch: /tmp/changelog/changelog.txz.sig appears to be truncated: 0/1332 bytes
@ jclendineng
# grep nameserver /etc/resolv.conf
nameserver 84.200.70.40
nameserver 80.69.100.214
nameserver 80.69.100.198
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 84.200.69.80
@ marjohn56
my config was already done on that way, on all interfaces.
-
Hi All,
i just found the "solution" for me. Changed the default Theme under Settings > General - to "rebellion" and the issue was "fixed"
THX for the suggestions on that issue.
-
I tried all those suggestions/supposed workarounds, but unfortunately, nothing worked for me. I can successfully trigger the update process via shell but not with the webinterface. Is there any development in this? Or is is seen as a small problem only happening in a few cases?
Thanks and best regards.
Update
I ended in reinstalling the whole system. Afterwards the update process worked again.
-
I just did that and it worked once, until I ran an upgrade and now it is broken again.
-
Also, make sure under System > General you have DNS servers such as 1.1.1.1 or 8.8.8.8
The trick on my system was also allocating at least one of your listed DNS servers to WAN (or the default gateway?) - I had them set to none previously...
-
That sounds like a possibility. Not sure exactly where to do that though...
My routing table is weird because it contains a seperate routing entry for each DNS I have set. I kinda assumed it would just use the default one.
-
System > Settings > General ... look for the DNS Servers and check what Gateway they are set to use.
-
My DNS is correct and I am still getting the error.
-
agh1701 (should that not be ncc?)
Try this and see if you get the same as me. On you workstation ping 130.225.254.116. Then try the same through the opnsense diagnostic tool. Go into ping and ping 130.225.254.116.
If yours is the same as mine you can ping that server from a machine connected to the network but you cannot ping it from the firewall/router itself.
-
Franco how a bout an other address with an up address in it will that work?
-
http://207.244.94.80/opnsense
Worked!
-
There is still something wrong. My dashboard says 18.7.7 however, my firmware page says the latest firmware is 18.7.6. I also noticed that when I did the upgrade there was no upgrade splash telling me what is new only packages.
-
Not for me. My Shell or anywhere else on the opnsense device itself cannot pin 207.244.94.80, or pretty much any other address.
I can happily ping 1.0.0.1 because this appears in my routing table courtesy of having a gateway defined with the DNS entry.
On this basis then if I go ahead and add a static route to the update cache I should be able to make it work.
-
And now I have it working by having put in a static route to 212.32.245.0/24. Obtained by doing an opnsense-update -M then pinging the route of the address returned.
I have no understanding of why I should have to do this and the default route just does not work locally on the device. It makes no sense.
For now at least it works
-
If this is an issue related to DNS, please explain why you are able to upgrade from console WITHOUT any issues at all. This is clearly a webgui update system issue, not related to DNS or anything else.