Unable to Check For Updates
-
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 -
That's fixed for me. Thanks.
-
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 -fWorked for me too. Thanks!
-
pkg update -f
pkg upgrade -fdid not help. I still have:
2.3.3-RELEASE-p1 (i386)
built on Thu Mar 09 07:17:43 CST 2017
FreeBSD 10.3-RELEASE-p16Unable to check for updates
Anybody an idea? Please.
Guenther
-
Got this same issue.. Dashboard claims 'unable to check for updates'.
I can see successful traffic to files00.netgate.com in tcpdump, and pkg update -f told me that all repositories are up to date. -
It is happening again. I'm running 2.4.0-RC (arm)
built on Wed Aug 23 01:13:55 CDT 2017
FreeBSD 11.0-RELEASE-p11It started at least late yesterday (31 Aug 2017) and is the same now.
oldunixguy
{Update]
I can do a packet capture but I'm not sure what to look for. Can you give me a hint at what the "Check for Update" transaction is like such as destination host, etc?oldunixguy
-
Just curious, is there a solution for this issue? We have the same issue running 2.3-RELEASE.
-
pkg-static update –f
pkg-static upgrade –fI'm a late upgrader, found this issue and running pkg -f was presented with missing libssl.so.8, switched to pkg-static and the update, upgrade worked… although, I did have to reboot the pfsense server afterwards to get things up and running.
-
Ok folks, this never addressed the issue I though it was addressing!
I need to connect a new PF box to the internet to get it updated. I have its WAN interface disabled and its hooked up to my local LAN. How do it get it to "see" the internet so i can update it???
My LAN is 1.x/22 (and has another PF box active as 1.1) and the new PF box is 3.1/22.
How in the world do i get a PF box to access the internet from just its LAN interface????? You can't tell it to use a GATEWAY in the LAN setup and adding the existing gateway of my Lan 1.1 PF box does not work, it says "gateway IP already exists"????
HELP!
Thanks,
MP
-
I need to connect a new PF box to the internet to get it updated. I have its WAN interface disabled and its hooked up to my local LAN. How do it get it to "see" the internet so i can update it???
My LAN is 1.x/22 (and has another PF box active as 1.1) and the new PF box is 3.1/22.
How in the world do i get a PF box to access the internet from just its LAN interface????? You can't tell it to use a GATEWAY in the LAN setup and adding the existing gateway of my Lan 1.1 PF box does not work, it says "gateway IP already exists"????;D
Hook up your second pfSense as a device on the lan of the first pfSense, which is hooked up to the net.
Activate it's WAN interface, activate DHCP on it, and it will update, upgrade, etc.
Hook yourself up to the LAN of this second pfSense box to pilot it (or use the console access).Think about it : a router/firewall with only one interface …. that's like a car without wheels ...
Ok folks, this never addressed the issue I though it was addressing!
It is actually not an issue ^^
-
Ok Thanks, I think Ii get it now, Lan interface on PFS is really WAN access for clients. So what you are saying is I must use the WAN interface for a 2nd PFS box hooked to my local LAN to get to the internet.
Thanks!
MP
-
pkg-static update –f
pkg-static upgrade –fI'm a late upgrader, found this issue and running pkg -f was presented with missing libssl.so.8, switched to pkg-static and the update, upgrade worked… although, I did have to reboot the pfsense server afterwards to get things up and running.
My problem matched yours and this worked perfectly. Thank you!
