Unable to Check For Updates
-
I'm still having this issue. I updated from console and rebooted but the problem still persists in the webgui.
-
The solution posted in the following thread worked for me when I had this problem, and turning the ram disk off and rebooting made no difference.
-
I am not using the RAMDISK option and still have this update issue.
I have been updating via the Console.
The Version Number/Built ON date has not been changing. It still shows 2.3-RC (i386)
built on Tue Apr 05 20:24:50 CDT 2016
FreeBSD 10.3-RELEASEI have tried several different DNS servers. All behave the same
-
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-base -
That was the solution - Thanks
All working well now. -
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-basethat worked for me too but it seems i've overshot the mark.
now on 2.3.1-DEVELOPMENT.
my update settings were set to automatically move to release.
is there any easy way to go back?
no big deal if not. just wanted to see the 2.3 release on the dash board.
-
Installing pfSense-base worked here as well (thank you!!!), and now I am in the same state as wireogue (on dev build 2.3.1.a.20160412.1222).
Is there a way to get back on the release train without a full reinstall?
Many thanks, and congratulations on getting a great release out the door!
-
i think the real question is… why are you guys still working?
shouldn't you take at least a week off to celebrate the 2.3 release?
get some cocaine and hookersplay some video games and watch porn?you're setting the bar kinda high. making the rest of us look bad.
just sayin'.
-
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-baseShould I do this also on the nanobad platform?
-
I'm in the same boat, can't update from 2.3 RC (2.3.r.20160406.0534) to 2.3 Release.
If I select "Keep following 2.3 dev snapshots" I can update past 2.3 Release. (2.3.1.a.20160412.1222 as of tis morning)
If I select "follow 2.3 snaps and move to release (default)" I get errors.I'm guessing that I have no IPV6 or other network issues since the stay dev option works.
Any ideas?
Can I just DL 2.3 Release manually and do an upgrade that way?
-
If you were on an RC or earlier, it's normal for it to offer 2.3.1.a. When you choose to upgrade, it will see -RELEASE and use that instead. There's an open ticket to fix that for the next version.
-
I did a clean install and came across as the same problem "Unable to Check For Updates":
I had to install the sarg manually, but before you install, it was necessary to update the package pkg-1.6.2 for pkg-1.7.2. After I upgraded this package the message "Unable to Check For Updates" appeared (even in a clean installation).
-
Clean 2.3 Release install?
If you go to update settings and select dev path, does it give you an option to update to 2.3.1? -
I had to do the following commands to get mine to work.
fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406pkg updatepkg install pfSense-base -
Ok, the fetch worked for me, I'm up at 2.3 Release now.
-
I upgraded my production pfSense and ran into the same problem and was unable to access the System>Update as it just froze the GUI.
For me the issue is I am running IPv6, however the Internet WAN IPv6 subnet is not advertised through BGP only my DMZ v6 space.
Switched the pfSense to prefer IPv4 and all is how it was before.Would be really nice to be able to bind all the internal services to a specific Interface and not have it default to the outbound Interface.
We don't advertise the internal links between our peering point and the DMZ for IPv6.Anyway, switching to prefer IPv4 solved it for me.
-
Was getting this:
[2.3-RC][admin@pfsense001]/root: pfSense-upgrade -4
Updating repositories metadata…
Updating pfSense-core repository catalogue...
Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
pkg: No trusted public keys found
repository pfSense-core has no meta file, using default settings
Fetching packagesite.txz: . done
pkg: No trusted public keys found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
pkg: No trusted public keys found
repository pfSense has no meta file, using default settings
Fetching packagesite.txz: .......... done
pkg: No trusted public keys found
Unable to update repository pfSenseDid this from the CLI - then was able to update.
fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406 -
-
@cmb:
Nope! Still "unable to check for updates" error, and no way to update manually…nice!
If you're still getting that at this point, you likely have connectivity issues. First guess, the system thinks it has IPv6 connectivity and it doesn't, but could be any number of things. SSH in, option 8, run:
pfSense-upgrade -4what's that get you?
There was a problem "unable to check for updates"
Thank you ! "PfSense-upgrade -4" helped! -
followed the steps to in shell/console:
pkg install pfSense-base
once installed and went back to gui, and it upgraded from
2.3.1-RELEASE (amd64)
built on Tue May 17 18:46:53 CDT 2016to
2.3.2-RELEASE (amd64)
built on Tue Jul 19 12:44:43 CDT 2016and
Version 2.3.3.a.20160801.2222 is available
