AutoConfigBackup: Unable to restore.
-
I did a fresh install to 2.1.2. When attempting to restore using AutoConfigBackup I get "SHA256 values do not match, cannot restore." Both hashes match, except for a <> separating the lines.
-
Yeah, I've got this too.
-
I also have this. Any ideas?
-
cmb has fixed it: https://github.com/pfsense/pfsense-packages/commit/075721b1e3cdf77a9e4691aa894f3c3ce391e344
Install the latest version 1.23 of AutoConfigBackup -
Do you know how long it usually takes to show up in the package manager? It still only shows 1.22
I also looked here but it doesn't show. http://files.pfsense.org/packages/8/All/
-
It's 1.23 on both the package servers (HTTP to www if pre-2.1.1, HTTPS to packages.pfsense.org 2.1.1 and later). Normally they sync every 15 minutes, but I actually logged into both of them and synced them manually right after I committed the change yesterday, so it's been available since 15:00 US Central time on the 11th.
If you're actually pulling a file from our servers, you'll see v 1.23 here.
https://packages.pfsense.org/packages/pkg_config.8.xml
http://www.pfsense.com/packages/pkg_config.8.xmlI'm not sure how you could still be seeing 1.22 at the time you last posted. Maybe if you couldn't reach the package server for some reason (it hasn't been down at all) and it used a cached package file, but it would clearly prompt you of that if it were the case. Maybe if you changed your package server to point to a non-default location, in which case you're not getting the updated files we have on our servers. Maybe if your system is behind a caching proxy of some sort that's serving the old file from its cache.
I also looked here but it doesn't show. http://files.pfsense.org/packages/8/All/
It doesn't need a PBI so there aren't any packages in that location for it.
-
@cmb:
I'm not sure how you could still be seeing 1.22 at the time you last posted. Maybe if you couldn't reach the package server for some reason (it hasn't been down at all) and it used a cached package file, but it would clearly prompt you of that if it were the case. Maybe if you changed your package server to point to a non-default location, in which case you're not getting the updated files we have on our servers. Maybe if your system is behind a caching proxy of some sort that's serving the old file from its cache.
Why do I still see 1.22 here? https://packages.pfsense.org/packages/config/autoconfigbackup/autoconfigbackup.xml
-
Why do I still see 1.22 here?
Because that is a "bonus" place where a version string can be stored. I don't think that is used or displayed anywhere. Bit of a pest, as people will always forget about it.
-
Why do I still see 1.22 here?
Because that is a "bonus" place where a version string can be stored. I don't think that is used or displayed anywhere. Bit of a pest, as people will always forget about it.
Frankly, I'd say the entire package should be "self-contained". So, that "bonus" place would sound like something that is required, unlike the pkg_config.<version>.xml{,<arch>}</arch></version> thing which makes really no sense to me why does it even exist (if anything, should IMO be autogenerated from the actual packages) and why those things are not in <packagename>.xml shipped with each package instead. (And yeah, "people will always forget about it" would sound like a good reason to fix the design.)</packagename>
-
I am on AutoConfigBackup v1.21 it appears, all other packages updated without issue however this one will not allow to be updated nor uninstalled ? .. Any ideas on how to resolve this issue ? .. All other functions appear to be running without issue on the update to v2.12
-
From this post by JimP: https://forum.pfsense.org/index.php?topic=75061.msg409576#msg409576
rm /etc/inc/crypt_acb.php /usr/local/pkg/autoconfig*That will clean up the old stuff and let you use the GUI to install the latest version, which is 1.23 at this time.
-
I have 1.23 installed but I'm still having an issue.
My key differs slightly in that there is a "test" string on the key, see attached.There is a test checkbox on the setup screen where you configure autoconfigbackup.
Could "test" have been added to the key that way?
-
The 2nd string (after the <>) is what comes from the AutoConfigBackup server. So it seems that it is spitting out "test" before the actual SHA string. I just tried it on my test 2.2-ALPHA system and got the same thing:
The following input errors were detected: SHA256 values do not match, cannot restore. bde1e9eacd068dcd9fcd216def92019cda50f06b51a13dc96133a6d9ceb77209 <> test bde1e9eacd068dcd9fcd216def92019cda50f06b51a13dc96133a6d9ceb77209I will email to support, because they might not see this quickly.
-
Forgot to copy one of the stock files back into place after our debugging last week, sorry about that. All good now.