Unable to Check For Updates
-
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
-
one can also resolve this issue via making following two changes
- change theme on firewall to default theme of pfSense.
- Try changing the architecture/type of firewall in update settings (I ran into such issue when I restored x86 config on my x64 firewall after which it was showing no updates available until when I changed its architecture to x64).
-
Had the "cannot check for updates" problemos also after upgrading to 2.3.1
Checked the dns resolving ok…. Switched off the ram disk
Pressed save @ the system-->update several times. Also changed the update source to experimental and back to stable.
Did check prefer ipv4 was ticked. Several reboots etc etc...No work, no joy.
FIX
SSH--> to pfsense box and choose option 8 (shell) input --> pfSense-upgrade -4
This also updates/installs "pfSense-base" component.
Reboot ---> All working like a toilet in a train
cheers:kekke
-
@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?
Thanks, working.
-
Same thing just happened to me but got it fixed by going to System > Routing and setting the WAN gateway as default gateway instead of the LAN gateway.
-
I had those issues in August, and then the dashboard changed from "unable to check for updates" to "version 2.3.2 available".
I am running a 2.3.1-RELEASE version on a specific machine, and had no time to upgrade while I had time. I upgraded other pfsense machines, but not that one (the main server, that has 11 IPSec VPNs running, and could not have an interruption until this time of the year).
And now, the 2.3.2-p1 is there, and the same problem comes again : "unable to check for updates" in the dashboard. I can't access to the console of the machine (it is a Virtual Machine hosted by a provider that gives me no console to the VMs), so I can't do it manually.
Is there a way to configure something in the GUI to make a workaround?
Thank you all (next ime, I'll do the upgrades whenever I see it's possible!)
-
Same thing just happened to me but got it fixed by going to System > Routing and setting the WAN gateway as default gateway instead of the LAN gateway.
Similar situation for me. I had an old tunnelbroker IPv6 tunnel that I had deleted, but did not delete the default gateway (it was disabled, but listed at the top of the gateways). Once I deleted this disabled gateway, the Updates were shown on the main screen. Thanks for the tip.
-
I did manual update because I had "Unable to check for updates" running 2.3.2 with pfSense-upgrade -4
I'm now on 2.3.3-RELEASE-p1 - fine, but again "Unable to check for updates"!
Any solution? -
I did manual update because I had "Unable to check for updates" running 2.3.2 with pfSense-upgrade -4
I'm now on 2.3.3-RELEASE-p1 - fine, but again "Unable to check for updates"!
Any solution?Nobody?
-
I think it's related as i am getting: "The system is on a later version than the official release." while on official release.
2.3.3-RELEASE (amd64)
built on Thu Feb 16 06:59:53 CST 2017
FreeBSD 10.3-RELEASE-p16Also, if i go to update settings it's showing wrong version while in settings it's on branch Stable (Default):
Current Base System
2.3.3
Latest Base System
0.19~Sergei
-
I was getting this too on a fresh 2.3.3 build earlier today.
try getting to a console/ssh and issuing:pkg update -f pkg upgrade -f
