GUI System Update - Unable to retrive system versions.
-
As the subject indicates.. GUI System Update is unable to retrieve system versions. Dashboard info widget doesn't seem have any trouble identifying the version though.
2.3-RC (i386)
built on Wed Apr 06 05:34:44 CDT 2016
FreeBSD 10.3-RELEASEAlso why does "System Update" link to back to the dashboard? Seems that either the link url or text should be changed to match the other.
See image attachments for additional details.
-
Click on Save on the Update settings page and it should sort itself out.
Greg
-
I seem to have the same issue since the last few days.
First GUI told me there was an update, but when I tried to get it, it would fail.
I tried clicking save on the update settings page, rebooted…
Now GUI tell me there is no update available. I'm currently running:
2.3-RC (amd64)
built on Wed Apr 06 05:34:38 CDT 2016
FreeBSD 10.3-RELEASEI've tried clicking Save on the update page with both different options - no matter what, GUI now tells me no updates available.
My WAN IP is dynamic, but is currently: 47.55.234.165
-
2.3.r.20160406.0534 is the latest version … so no newer versions than what you have now
-
Interesting. Well that sounds encouraging then.
Though, yesterday, the GUI was definitely telling me there was an updated version, dated April 7. That was before I hit save on the Update Setting Page though, so I don't know what url it was hitting… But that April 7th version would fail when I tried to update to it. So quite possibly it was looking at the wrong/old URL for updates.
Sounds like all is fine now, if there have been no updates for a couple of days...
-
2.3.r.20160406.0534 is the latest version … so no newer versions than what you have now
Yes but that shouldn't result in a failure.
-
Click on Save on the Update settings page and it should sort itself out.
Greg
Why do you think clicking on save will fix this? It didn't by the way.
-
Why do you think clicking on save will fix this? It didn't by the way.
https://forum.pfsense.org/index.php?topic=109370.msg608935#msg608935
I had your error plus the ones at the above post and saving the update setting again fixed both.