Snapshot auto-update problem
-
Right. The new link is in the first post of this thread. :)
-
Right. The new link is in the first post of this thread. :)
Nope. I changed it to
http://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_HEAD/.updaters/Rebooted, still does not work.
-
Hmm.. Works fine for the three boxes I have 2.2 on and seems to be working find for everyone else.
Can you access that link from a browser on your system?
-
Can you access that link from a browser on your system?
Yep, comes right up on my browser.
UPDATE: Here is the deal. If you are on the absolute latest version, you get the error message "Unable to check for updates". If you are not on the latest version, then it looks like it is working normally.
-
Just updated my test box…
2.2-BETA (amd64)
built on Fri Oct 24 12:17:25 CDT 2014
FreeBSD 10.1-RC3Can you give us a play by play as to what happens when you try to update?
-
Like I said above, I am now on "built on Thu Oct 23 15:31:34 CDT 2014".
Since there is no new update available, the dashboard says "Unable to check for updates."When another update is made available, the error message "Unable to check for updates." is replaced with the new update available message.
-
When another update is made available, the error message "Unable to check for updates." is replaced with the new update available message.
Actually it should say "You are on the latest version"
"Unable to check for updates" means the box is unable to connect and check.
Your box either has a connectivity problem or the path has been entered wrong.
You can try downloading the new update from snapshots.pfsense.org and do a manual update…
ON your box go to Diagnostics/DNS Lookup and do a lookup for pfsense.org
-
I haven't changed anything. It is a fresh load, and not an upgrade. I did a cut and paste of the upgrade URL. That means this is a bug.
-
I split this topic since it was unrelated to the URL change.
It's not likely a bug, but a problem in your DNS or upstream connectivity from the box itself. "Unable to check for updates" is not what it says when there is no new version. That is what shows when it cannot contact the update server. If you were on the most recent version it would say "You are on the latest version."
-
It is doing exactly what I say that it is above. If you want the details of my hardware, go look through the 2.2 crash submissions yesterday. My machine is the APU1c bug report that uploaded yesterday after a crash. I'm on Comcast so there isn't anything else upstream but them….
-
It works for me on an APU with https://snapshots.pfsense.org/FreeBSD_stable/10/amd64/pfSense_HEAD/.updaters/ or https://snapshots.pfsense.org/FreeBSD_releng/10.1/amd64/pfSense_HEAD/.updaters/
Using the amd64 version, full install.
Crash reports must be looked up by IP and submission timestamp. We can't look them up by what sort of system submitted the report.
