# Core 201 Testing Error **URL:** \ **Category:** Testing\ **Created:** [12 March 2026 12:01 UTC](https://community.ipfire.org/t/core-201-testing-error/15594 "2026-03-12T12:01:22Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![tratru](https://community.ipfire.org/user_avatar/community.ipfire.org/tratru/32/8787_2.png) [@tratru](https://community.ipfire.org/u/tratru)\ **Post date:** [12 March 2026 12:01 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/1 "2026-03-12T12:01:22Z")
Hi, I tried installing the latest test version on a test virtual machine, but I can’t update my machine, giving me an error. ![upgrade](https://community.ipfire.org/uploads/default/original/2X/f/f70d981b1c0033ebca67a973edce530a766dcd4b.jpeg) > | 12:58:02 | pakfire: | PAKFIRE INFO: Pakfire has finished. Closing. | | --- | --- | --- | | 12:58:02 | pakfire: | TIME INFO: Time Server 195.32.70.195 has -0.000816 sec offset to localtime. | | 12:58:02 | pakfire: | DOWNLOAD ERROR: The downloaded file (pakfire2/2.29.1-x86\_64/paks/core-upgrade-2.29-200.ipfire) wasn’t verified by [IPFire.org](http://IPFire.org). Sorry - Exiting… | | 12:58:00 | pakfire: | DOWNLOAD INFO: File received. Start checking signature… | | 12:58:00 | pakfire: | DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK | | 12:55:49 | pakfire: | DOWNLOAD INFO: pakfire2/2.29.1-x86\_64/paks/core-upgrade-2.29-200.ipfire has size of 124221330 bytes | | 12:55:48 | pakfire: | DOWNLOAD INFO: Host: [mirror1.ipfire.org](http://mirror1.ipfire.org) (HTTPS) - File: pakfire2/2.29.1-x86\_64/paks/core-upgrade-2.29-200.ipfire | | 12:55:48 | pakfire: | MIRROR INFO: 1 servers found in list | | 12:55:48 | pakfire: | DOWNLOAD STARTED: paks/core-upgrade-2.29-200.ipfire | | 12:55:48 | pakfire: | CORE UPGR: Upgrading from release 199 to 201 | | 12:55:48 | pakfire: | CORE INFO: core-list.db is 5 seconds old. - DEBUG: noforce | | 12:55:48 | pakfire: | CORE INFO: Checking for Core-Updates… | | 12:55:48 | pakfire: | PAKFIRE INFO: IPFire Pakfire 2.29.1-x86\_64 started! | | 12:55:43 | pakfire: | PAKFIRE INFO: Pakfire has finished. Closing. | | 12:55:43 | pakfire: | DOWNLOAD FINISHED: pakfire2/2.29.1-x86\_64/lists/core-list.db | | 12:55:43 | pakfire: | DOWNLOAD INFO: Signature of core-list.db is fine. | | 12:55:43 | pakfire: | DOWNLOAD INFO: File received. Start checking signature… | | 12:55:43 | pakfire: | DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK | | 12:55:42 | pakfire: | DOWNLOAD INFO: pakfire2/2.29.1-x86\_64/lists/core-list.db has size of 903 bytes | | 12:55:42 | pakfire: | DOWNLOAD INFO: Host: [mirror1.ipfire.org](http://mirror1.ipfire.org) (HTTPS) - File: pakfire2/2.29.1-x86\_64/lists/core-list.db | | 12:55:42 | pakfire: | MIRROR INFO: 1 servers found in list | | 12:55:42 | pakfire: | DOWNLOAD STARTED: lists/core-list.db | | 12:55:42 | pakfire: | CORE INFO: core-list.db is 13 seconds old. - DEBUG: force | | 12:55:42 | pakfire: | DOWNLOAD FINISHED: pakfire2/2.29.1-x86\_64/lists/packages\_list.db | ---
**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\ **Post date:** [12 March 2026 20:01 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/2 "2026-03-12T20:01:24Z")
> [@tratru](#): > > | 12:58:02 | pakfire: | PAKFIRE INFO: Pakfire has finished. Closing. | > | --- | --- | --- | > | 12:58:02 | pakfire: | TIME INFO: Time Server 195.32.70.195 has -0.000816 sec offset to localtime. | It’s a problem with the time synchronization with the server. ---
**Author:** ![rodneyp](https://community.ipfire.org/user_avatar/community.ipfire.org/rodneyp/32/16575_2.png) [@rodneyp](https://community.ipfire.org/u/rodneyp)\ **Post date:** [12 March 2026 21:58 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/3 "2026-03-12T21:58:35Z")
My testing installation is set to the default of syncronise time daily. Upgrade to CU201, via WUI, completed without problems. I have few addons, but libxxhash did also upgrade. Reboot, via WUI, also went smoothly. ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [14 March 2026 21:15 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/4 "2026-03-14T21:15:55Z")
> [@pscar13](#): > > It’s a problem with the time synchronization with the server. I would doubt that it is a time sync issue. The delta is 0.8 milliseconds. In the code for checking the signature, if it fails it checks if it can access the time server. If it can access the server then it shows the message that was provided, showing the time info in case the delta is too high. If it is too high then the gpg --verify signature check will fail but a fraction of a millisecond will not cause that problem. The file was successfully downloaded > [@tratru](#): > > DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK so I think the most likely thing is that there was some corruption during that download that didn’t cause a break in the download itself, so it completed. However that corrupted download then failed the gpg --verify check of the file downloaded. I would try the update again and see if it repeats or not. ---
**Author:** ![tratru](https://community.ipfire.org/user_avatar/community.ipfire.org/tratru/32/8787_2.png) [@tratru](https://community.ipfire.org/u/tratru)\ **Post date:** [15 March 2026 14:31 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/5 "2026-03-15T14:31:36Z")
Hi, I tried updating my test installation, and it worked without a hitch. ---
**Author:** ![arno\_triple](https://community.ipfire.org/user_avatar/community.ipfire.org/arno_triple/32/8277_2.png) [@arno\_triple](https://community.ipfire.org/u/arno_triple)\ **Post date:** [15 March 2026 18:01 UTC](https://community.ipfire.org/t/core-201-testing-error/15594/6 "2026-03-15T18:01:10Z")
Same here, no problems so far.