2.6.0 - Installed Pkgs - Unable to retrieve package information.
-
@fabrizior Having the exact same issue with 2.6.0. On Dashboard it also show „Unable to check for update“
Also GUI is kind of slow/bugged yes.
-
@fabrizior Do you have multi WAN setup?
-
Exactly the same issue here, update page and package manager page of the GUI won't load, just hangs. Used to work a day or two ago.
I guess those pages are reaching out to external URLs that are down?
-
Think i saw some issue related to "check for update preferring ipv6" if possible , on the forum.
Do you have a working ipv6 setup ?Anyway i just have ipv4 here at home.
And yesterday reinstalled my homebox from scratch (usb) w. 2.6.0 , and i had no issues reinstalling the packets.
Nor did i have any issues registering my pfSense+ key , and upgrade to 22.01I did see & report "similar" issue if i pointed my 2.6.0 to the plus upgrade repos 4 days ago.
https://forum.netgate.com/topic/171004/solved-upgrading-from-2-6-0-to-plus-unable-to-check-for-updates
But it was fixed quite fast, and i think it was a CERT error on the plus section.I had no issues if i reverted to pointing at the 2.6.0 repos.
Not much help , but it was working for me yesterday, using ipv4.
/Bingo
-
@bingo600 ah yes! I checked "prefer IPv4" and now it works again! Seems their repo must still be having IPv6 issues!
Thank you :)
-
Thanks, that fixed it for me as well! IPv6 was the problem.
-
@mrsunfire
no… just one set of ipv4 and ipv6 gateways for a single wan interface.
though I have openvpn and wireguard (remote access, not site-to-site) configured -
perhaps an enhancement request on redmine is in-order to catch the timeouts or faults against the package repo and provide a properly i formative error msg?
-
@mrsunfire why is ipv6 an issue? hasn’t been a problem in the past?!
-
@fabrizior I think the fault is on Netgate side as they having issues with IPv6 connectivity.
-
@jan8p I turned on debugging and it looks like at least one repository isn't working on IPv6?
e.g. ping pkg01-atx.netgate.com works but ping6 pkg01-atx.netgate.com doesn't and the GUI/default is for scripts to use IPv6 over IPv4...
-
@jan8p I checked prefer IPv4 in adv. settings... and saved. System > Update and Package manager are still having connection faults. Did I miss a step?
-
@fabrizior said in 2.6.0 - Installed Pkgs - Unable to retrieve package information.:
are still having connection faults. Did I miss a step?
Goto console or SSH, option 8 and
ps ax | grep 'pkg'if you see any pkk update" instances, you have to wait before they time out.
Or kill them.See also https://forum.netgate.com/topic/171103/unable-to-check-for-updates/6?_=1648452964596
-
@fabrizior I just did the same and it seems to have fixed the issue, though clearly NetGate should fix their side - imagine this tick box is to help people who haven't got IPv6 working locally for whatever reason...
-
@thondwe said in 2.6.0 - Installed Pkgs - Unable to retrieve package information.:
though clearly NetGate should fix their side
Netgate isn't an ISP, neither peering company. Their servers have the correct IPv6 setup.
IMHO : This issue is between them and us.And the issue isn't visible for all of us.
-
@fabrizior All I did extra is a reboot....not sure if that is required though!
-
@gertjan Running a tracert on IPv4 gets me 13 steps to pkg01-atx.netgate.com and looks to get to Zcolo - so Co location Company that's part of ZAYO?
Run the tracert on IPv6 30(!) steps a lot of which timeout. Both seem to reference ZAYO - hop 9 on IP4 and hop 11 on IPv6.
So you might well be right and it's an IPV6 routing problem in the co-lo company where Netgate have their servers??
-
@gertjan took a few minutes but the ipv4 workaround has now been working reliably. thanks all.
-
@thondwe said in 2.6.0 - Installed Pkgs - Unable to retrieve package information.:
pkg01-atx.netgate.com
How many different package servers are there? Anyone have a list? will add to my telegraf monitoring. Want to see how (un)reliable these are over time.
-
@fabrizior said in 2.6.0 - Installed Pkgs - Unable to retrieve package information.:
ipv4 workaround has now been working reliably
