# Update Trouble

**URL:** https://community.ipfire.org/c/installing-and-running-ipfire/update-trouble/26.md

[Latest](https://community.ipfire.org/latest.md) · [Categories](https://community.ipfire.org/categories.md)

---

## [About the Update Trouble category](https://community.ipfire.org/t/about-the-update-trouble-category/3465)

<div class="topic-metadata">

**Author:** [@ms](https://community.ipfire.org/u/ms)\
**Replies:** 0\
**Last updated:** [15 October 2020 09:37 UTC](https://community.ipfire.org/t/about-the-update-trouble-category/3465 "2020-10-15T09:37:46Z")

</div>

Troubleshoot failed or problematic Core Updates and package upgrades

---

## [Web UI and /var/lib/knot-resolver/leases.db mismatch](https://community.ipfire.org/t/web-ui-and-var-lib-knot-resolver-leases-db-mismatch/16015)

<div class="topic-metadata">

**Author:** [@barneyklarnocks](https://community.ipfire.org/u/barneyklarnocks)\
**Replies:** 10\
**Last updated:** [29 October 2026 21:46 UTC](https://community.ipfire.org/t/web-ui-and-var-lib-knot-resolver-leases-db-mismatch/16015 "2026-10-29T21:46:40Z")

</div>

Hi - (Edited to remove spurious reference to work queue API.) I’ve long been running IPFire, progressively upgraded over time. I’ve had recurring issues with DNS name resolution within my network breaking periodically …

---

## [Core 164: Module nf\_log\_ipv4 not found in directory](https://community.ipfire.org/t/core-164-module-nf-log-ipv4-not-found-in-directory/7552)

<div class="topic-metadata">

**Author:** [@larsen](https://community.ipfire.org/u/larsen)\
**Replies:** 20\
**Last updated:** [29 October 2026 10:12 UTC](https://community.ipfire.org/t/core-164-module-nf-log-ipv4-not-found-in-directory/7552 "2026-10-29T10:12:13Z")

</div>

I got this error when upgrading from 163 to 164: Setting up firewall modprobe: FATAL: Module nf\_log\_ipv4 not found in directory /lib/modules/5.15.6-ipfire iptables: No chain/target/match by that name. iptables: No chain…

---

## [Ipfire update from core 203 -\> Core 204 does not](https://community.ipfire.org/t/ipfire-update-from-core-203-core-204-does-not/16241)

<div class="topic-metadata">

**Author:** [@ritchie](https://community.ipfire.org/u/ritchie)\
**Replies:** 13\
**Last updated:** [28 October 2026 16:22 UTC](https://community.ipfire.org/t/ipfire-update-from-core-203-core-204-does-not/16241 "2026-10-28T16:22:54Z")

</div>

Hi, I have Update my System today to core 204 and the System does not reboot correct now. Web Seite ist not shown, Clients are not Going online. I need helpdesk to get the System running. Best regards Ritchie

---

## [Perl JSON.pm Module was removed by the core update 204](https://community.ipfire.org/t/perl-json-pm-module-was-removed-by-the-core-update-204/16242)

<div class="topic-metadata">

**Author:** [@ritchie](https://community.ipfire.org/u/ritchie)\
**Replies:** 6\
**Last updated:** [28 October 2026 15:46 UTC](https://community.ipfire.org/t/perl-json-pm-module-was-removed-by-the-core-update-204/16242 "2026-10-28T15:46:09Z")

</div>

Hello Together, after getting the system back to running, I noticed that the perl-Module JSON.pm is not installed on my system anymore. Will be this module included in some of the other perl-modules I have already ins…

---

## [IPFire on Pi 4B](https://community.ipfire.org/t/ipfire-on-pi-4b/16199)

<div class="topic-metadata">

**Author:** [@ernieg92](https://community.ipfire.org/u/ernieg92)\
**Replies:** 16\
**Last updated:** [17 October 2026 08:23 UTC](https://community.ipfire.org/t/ipfire-on-pi-4b/16199 "2026-10-17T08:23:25Z")

</div>

First word, thanks to this community. IPFire is a great firewall and the community support is amazing. Last week I had a catastrophic failure of my hardware (knew it was coming; kept planning to replace; waited too long…

---

## [Core Update 203: Recommendations Before and After Upgrading](https://community.ipfire.org/t/core-update-203-recommendations-before-and-after-upgrading/16009)

<div class="topic-metadata">

**Author:** [@pscar13](https://community.ipfire.org/u/pscar13)\
**Replies:** 17\
**Last updated:** [19 September 2026 08:44 UTC](https://community.ipfire.org/t/core-update-203-recommendations-before-and-after-upgrading/16009 "2026-09-19T08:44:54Z")

</div>

If you are upgrading from an earlier IPFire version, or performing a fresh installation followed by restoring a backup created before CU203, the following steps are recommended after the upgrade. 1. Regenerate the DHCP …

---

## [\`location update\` failing to exit with 3 when database was already the latest version](https://community.ipfire.org/t/location-update-failing-to-exit-with-3-when-database-was-already-the-latest-version/16125)

<div class="topic-metadata">

**Author:** [@iconoclasthero](https://community.ipfire.org/u/iconoclasthero)\
**Replies:** 3\
**Last updated:** [4 September 2026 12:46 UTC](https://community.ipfire.org/t/location-update-failing-to-exit-with-3-when-database-was-already-the-latest-version/16125 "2026-09-04T12:46:02Z")

</div>

Since I would like to skip an export if “the database was already the latest version,” I wanted to be able to use the non-zero exit code to do so… Either the documentation is incorrect or there’s something wrong with lo…

---

## [Fatal error with knot in update core 203](https://community.ipfire.org/t/fatal-error-with-knot-in-update-core-203/16090)

<div class="topic-metadata">

**Author:** [@roberto](https://community.ipfire.org/u/roberto)\
**Replies:** 5\
**Last updated:** [23 August 2026 07:19 UTC](https://community.ipfire.org/t/fatal-error-with-knot-in-update-core-203/16090 "2026-08-23T07:19:32Z")

</div>

Hello again. I’m having this problem with an IPFire. IPFire diagnostics SecciÃ³n: dns Fecha: Agosto 19, 2026 10:54:50 supervisord: exited: kresd1 (exit status 1; not expected) 10:54:50 supervisord: captured stdio …

---

## [Pakfire upgrade to specific version](https://community.ipfire.org/t/pakfire-upgrade-to-specific-version/6907)

<div class="topic-metadata">

**Author:** [@anon42188109](https://community.ipfire.org/u/anon42188109)\
**Replies:** 13\
**Last updated:** [22 August 2026 18:55 UTC](https://community.ipfire.org/t/pakfire-upgrade-to-specific-version/6907 "2026-08-22T18:55:45Z")

</div>

I have a test env (on 159). Currently, the latest version is 162. Can pakfire upgrade to 160 and stop? From the pakfire command, \<upgrade\> will install the latest version of all paks. Thanks.

---

## [Error with addons update](https://community.ipfire.org/t/error-with-addons-update/16089)

<div class="topic-metadata">

**Author:** [@roberto](https://community.ipfire.org/u/roberto)\
**Replies:** 2\
**Last updated:** [19 August 2026 08:23 UTC](https://community.ipfire.org/t/error-with-addons-update/16089 "2026-08-19T08:23:15Z")

</div>

Hi, When trying to update add-ons on IPFire, I receive this result: Aug 19 09:54:29 bs pakfire: PAKFIRE INFO: IPFire Pakfire 2.29-x86\_64 started! Aug 19 09:54:29 bs pakfire: MIRROR INFO: server-list.db is 3602 seconds …

---

## [Core 203 update : errors with guardian](https://community.ipfire.org/t/core-203-update-errors-with-guardian/16007)

<div class="topic-metadata">

**Author:** [@ramfast](https://community.ipfire.org/u/ramfast)\
**Replies:** 1\
**Last updated:** [1 August 2026 11:23 UTC](https://community.ipfire.org/t/core-203-update-errors-with-guardian/16007 "2026-08-01T11:23:56Z")

</div>

Hi, Just wanted to update from core 202 to 203 but encountered this error with guardian update : Jul 24 14:32:23 ipfire pakfire: DOWNLOAD STARTED: meta/meta-guardian Jul 24 14:32:23 ipfire pakfire: MIRROR INFO: 19 ser…

---

## [Updating packfire](https://community.ipfire.org/t/updating-packfire/16023)

<div class="topic-metadata">

**Author:** [@mrelfire](https://community.ipfire.org/u/mrelfire)\
**Replies:** 3\
**Last updated:** [29 July 2026 11:22 UTC](https://community.ipfire.org/t/updating-packfire/16023 "2026-07-29T11:22:03Z")

</div>

I have a little glitch Jul 28 13:45:34 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.29-x86\_64 started! Jul 28 13:45:34 ipfire pakfire: MIRROR INFO: server-list.db is 103 seconds old. - DEBUG: force Jul 28 13:45:34 ipf…

---

## [Cu 203 knot-resolver openvpn not working](https://community.ipfire.org/t/cu-203-knot-resolver-openvpn-not-working/15982)

<div class="topic-metadata">

**Author:** [@urmelchen](https://community.ipfire.org/u/urmelchen)\
**Replies:** 16\
**Last updated:** [26 July 2026 07:51 UTC](https://community.ipfire.org/t/cu-203-knot-resolver-openvpn-not-working/15982 "2026-07-26T07:51:25Z")

</div>

ovpn-clients connect successfully, but name resolution seems not to work.

---

## [202-203: Suricata logging error, IPS not starting](https://community.ipfire.org/t/202-203-suricata-logging-error-ips-not-starting/15989)

<div class="topic-metadata">

**Author:** [@mangrove](https://community.ipfire.org/u/mangrove)\
**Replies:** 1\
**Last updated:** [22 July 2026 13:41 UTC](https://community.ipfire.org/t/202-203-suricata-logging-error-ips-not-starting/15989 "2026-07-22T13:41:33Z")

</div>

After update from 202 to 203 (it seems the IPS was NOT on in this system, which is strange, but that may itself be an error) the IPS would not start. The error was: \[7063\] \<Error\> -- unable to initialize sub-module eve…

---

## [Crash of knot-resolver with 203](https://community.ipfire.org/t/crash-of-knot-resolver-with-203/15988)

<div class="topic-metadata">

**Author:** [@o\_schlenker](https://community.ipfire.org/u/o_schlenker)\
**Replies:** 1\
**Last updated:** [22 July 2026 13:05 UTC](https://community.ipfire.org/t/crash-of-knot-resolver-with-203/15988 "2026-07-22T13:05:56Z")

</div>

After updating an ipfire box from 202 to 203 the box refused to do DNS resolving. Searching for the reason it turns out that the knot-resolver did crash, error log is attached. Further investigation regarding the crash…

---

## [202 to 203 upgrade , took out my default route?](https://community.ipfire.org/t/202-to-203-upgrade-took-out-my-default-route/15985)

<div class="topic-metadata">

**Author:** [@bigbloke](https://community.ipfire.org/u/bigbloke)\
**Replies:** 0\
**Last updated:** [21 July 2026 23:16 UTC](https://community.ipfire.org/t/202-to-203-upgrade-took-out-my-default-route/15985 "2026-07-21T23:16:09Z")

</div>

HI guys Sorry for not uploading this to bugzilla - I couldnt get the password code email delivered to my registered address to update the login - so sharing here as “no route to host” :slight\_smile: ! Running IPFire co…

---

## [DNS zones does not work after update](https://community.ipfire.org/t/dns-zones-does-not-work-after-update/15970)

<div class="topic-metadata">

**Author:** [@bbele](https://community.ipfire.org/u/bbele)\
**Replies:** 8\
**Last updated:** [21 July 2026 13:12 UTC](https://community.ipfire.org/t/dns-zones-does-not-work-after-update/15970 "2026-07-21T13:12:35Z")

</div>

Hi! I’ve just upgraded from Core Update 202 to 203 and DNS resolving through zones doesn’t work any more. I’m using 3 ipfire firewalls to simulate 3 datacenters. All of them are connected using Wireguard. I’ve set the …

---

## [Upgraded IPFire hardware, Omada access points stopped working](https://community.ipfire.org/t/upgraded-ipfire-hardware-omada-access-points-stopped-working/15966)

<div class="topic-metadata">

**Author:** [@bloater99](https://community.ipfire.org/u/bloater99)\
**Replies:** 9\
**Last updated:** [20 July 2026 10:47 UTC](https://community.ipfire.org/t/upgraded-ipfire-hardware-omada-access-points-stopped-working/15966 "2026-07-20T10:47:30Z")

</div>

I have a work network that is exclusively a “guest network”. There are almost no wired devices. Just an Omada controller and 6 access points. I had an opportunity to upgrade the IPFire hardware. I installed IPFire on…

---

## [Location Block settings and backup/restore](https://community.ipfire.org/t/location-block-settings-and-backup-restore/15887)

<div class="topic-metadata">

**Author:** [@dark0ipfire](https://community.ipfire.org/u/dark0ipfire)\
**Replies:** 13\
**Last updated:** [13 July 2026 16:02 UTC](https://community.ipfire.org/t/location-block-settings-and-backup-restore/15887 "2026-07-13T16:02:07Z")

</div>

While comparing source (CU197) / target (CU202) settings of a backup/restore procedure nearly everything looks perfect, but Location Block settings differ. While they where all (but Germany) set in the source system, som…

---

## [CU 201: No space left on device](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760)

<div class="topic-metadata">

**Author:** [@larsen](https://community.ipfire.org/u/larsen)\
**Replies:** 14\
**Last updated:** [9 July 2026 12:32 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760 "2026-07-09T12:32:55Z")

</div>

On updating from CU 200 to CU 201, I got an error message in /var/log/pakfire/update-core-upgrade-201.log: dracut\[I\]: Executing: /usr/bin/dracut --kver=6.18.7-ipfire --force dracut\[I\]: \*\*\* Including module: modsign \*\*\* …

---

## [No Green DNS on Blue Net after Core-Update 203](https://community.ipfire.org/t/no-green-dns-on-blue-net-after-core-update-203/15916)

<div class="topic-metadata">

**Author:** [@dr\_techno](https://community.ipfire.org/u/dr_techno)\
**Replies:** 2\
**Last updated:** [27 June 2026 17:31 UTC](https://community.ipfire.org/t/no-green-dns-on-blue-net-after-core-update-203/15916 "2026-06-27T17:31:01Z")

</div>

after updating to IPFire 2.29 (x86\_64) - Core-Update 203 Development Build: master/9b7ed567 Green DNS is not servicing Blue Network. I had to set Blue Network to a public DNS. How can I patch blue network to use Green D…

---

## [Custom urlfilter blacklists disappear in version 200](https://community.ipfire.org/t/custom-urlfilter-blacklists-disappear-in-version-200/15623)

<div class="topic-metadata">

**Author:** [@lrez](https://community.ipfire.org/u/lrez)\
**Replies:** 6\
**Last updated:** [23 June 2026 20:46 UTC](https://community.ipfire.org/t/custom-urlfilter-blacklists-disappear-in-version-200/15623 "2026-06-23T20:46:06Z")

</div>

Hello, we’ve been using several custom blacklists created via the blacklist editor in the web interface in IPFire for a long time. We also use the Toulouse blacklist source. These manually created blacklists were always …

---

## [After CU202 trouble with unbound](https://community.ipfire.org/t/after-cu202-trouble-with-unbound/15897)

<div class="topic-metadata">

**Author:** [@pygr](https://community.ipfire.org/u/pygr)\
**Replies:** 3\
**Last updated:** [19 June 2026 09:17 UTC](https://community.ipfire.org/t/after-cu202-trouble-with-unbound/15897 "2026-06-19T09:17:25Z")

</div>

Several hours after the upgrade, DNS queries from hosts on my LAN started failing after running for months without a problem. Thinking that maybe a fix was available through a Pakfire update, I tried that. What I got was…

---

## [Core version 202, language switching results in garbled characters](https://community.ipfire.org/t/core-version-202-language-switching-results-in-garbled-characters/15864)

<div class="topic-metadata">

**Author:** [@fxneng](https://community.ipfire.org/u/fxneng)\
**Replies:** 9\
**Last updated:** [10 June 2026 05:52 UTC](https://community.ipfire.org/t/core-version-202-language-switching-results-in-garbled-characters/15864 "2026-06-10T05:52:33Z")

</div>

After updating to core version 202, the menu displayed garbled characters when switching between Simplified and Traditional Chinese. After investigation, it was found to be a problem with header.pl, which lacked support …

---

## [Rare files in /var/log/suricata](https://community.ipfire.org/t/rare-files-in-var-log-suricata/15845)

<div class="topic-metadata">

**Author:** [@roberto](https://community.ipfire.org/u/roberto)\
**Replies:** 1\
**Last updated:** [1 June 2026 07:30 UTC](https://community.ipfire.org/t/rare-files-in-var-log-suricata/15845 "2026-06-01T07:30:33Z")

</div>

Hi, I still have IPFire version 201 on my device, and looking at the logs, I’ve seen some strange files that take up 1.2GB. Are these normal? Thanks!,

---

## [Downfall (CVE-2022-40982) — 202?](https://community.ipfire.org/t/downfall-cve-2022-40982-202/15833)

<div class="topic-metadata">

**Author:** [@sec-con](https://community.ipfire.org/u/sec-con)\
**Replies:** 3\
**Last updated:** [30 May 2026 17:29 UTC](https://community.ipfire.org/t/downfall-cve-2022-40982-202/15833 "2026-05-30T17:29:24Z")

</div>

Has the Downfall microcode update not been released with 202? Any way I can check or run that manually, or is it the kernel that has not been updated? (No other issues or questions about 202 :+1: )

---

## [CU202: French accents problem in WUI](https://community.ipfire.org/t/cu202-french-accents-problem-in-wui/15816)

<div class="topic-metadata">

**Author:** [@pscar13](https://community.ipfire.org/u/pscar13)\
**Replies:** 14\
**Last updated:** [28 May 2026 13:43 UTC](https://community.ipfire.org/t/cu202-french-accents-problem-in-wui/15816 "2026-05-28T13:43:55Z")

</div>

CU202: Modifying the openbox method in header.pl broke French accents And more …

---

## [CU202 - Zabbix has stopped reporting OpenVPN status](https://community.ipfire.org/t/cu202-zabbix-has-stopped-reporting-openvpn-status/15820)

<div class="topic-metadata">

**Author:** [@filabrasileiro](https://community.ipfire.org/u/filabrasileiro)\
**Replies:** 4\
**Last updated:** [28 May 2026 06:03 UTC](https://community.ipfire.org/t/cu202-zabbix-has-stopped-reporting-openvpn-status/15820 "2026-05-28T06:03:11Z")

</div>

Hello Community, anyone else has faced an issue after CU202 with Zabbix plugin 7.0.21-21 that the OpenVPN connection state or expired certificate notification is not coming anymore for the users? Best regards

---

## [Trouble Ugrading from 200 to 202 Latest](https://community.ipfire.org/t/trouble-ugrading-from-200-to-202-latest/15798)

<div class="topic-metadata">

**Author:** [@cbrown](https://community.ipfire.org/u/cbrown)\
**Replies:** 1\
**Last updated:** [19 May 2026 17:16 UTC](https://community.ipfire.org/t/trouble-ugrading-from-200-to-202-latest/15798 "2026-05-19T17:16:18Z")

</div>

Tried to upgrade to latest cu202 but failed with … May 19 10:55:38 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.29.1-x86\_64 started! May 19 10:55:38 ipfire pakfire: CORE INFO: Checking for Core-Updates... May 19 10:55…

[Next page](https://community.ipfire.org/c/installing-and-running-ipfire/update-trouble/26.md?page=1)
