Cannot upgrade via pakfire

Networking
1

Hello… I realized recently that I am unable to connect to IPFire’s update service . Anyone seen this before? Thank you

Aug 31 19:24:34 ipfire pakfire: CORE INFO: core-list.db is 142872 seconds old. - DEBUG: force
Aug 31 19:24:34 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Aug 31 19:24:34 ipfire pakfire: MIRROR INFO: 26 servers found in list
Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: Host: mirrors.up.pt
(HTTPS) - File: pub/ipfire/pakfire2/2.25-x86_64/lists/core-list.db
Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: pub/ipfire/pakfire2/2.25-x86_64/lists/core-list.db has size of bytes
Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500

  • 500 Can’t connect to mirrors.up.pt:443 (Name or service not known)
    Aug 31 19:24:34 ipfire pakfire: Giving up: There was no chance to
    get the file lists/core-list.db from any available server. There was an
    error on the way. Please fix it.
    Aug 31 19:24:34 ipfire pakfire: CORE UPGR: Upgrading from release 146 to 147
    Aug 31 19:24:34 ipfire pakfire: DOWNLOAD STARTED: meta/meta-core-upgrade-147
    Aug 31 19:24:34 ipfire pakfire: MIRROR INFO: 26 servers found in list
    Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: Host: muug.ca (HTTPS)
  • File: mirror/ipfire/pakfire2/2.25-x86_64/meta/meta-core-upgrade-147
    Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: mirror/ipfire/pakfire2/2.25-x86_64/meta/meta-core-upgrade-147 has size of bytes
    Aug 31 19:24:34 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500
  • 500 Can’t connect to muug.ca:443 (Name or service not known)
    Aug 31 19:24:34 ipfire pakfire: Giving up: There was no chance to
    get the file meta/meta-core-upgrade-147 from any available server. There
    was an error on the way. Please fix it.
    Aug 31 19:24:34 ipfire pakfire: No filename given in meta-file.
    Aug 31 19:31:55 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
    Aug 31 19:31:55 ipfire pakfire: CORE INFO: core-list.db is 143313 seconds old. - DEBUG: force
    Aug 31 19:31:55 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
    Aug 31 19:31:55 ipfire pakfire: MIRROR INFO: 26 servers found in list
    Aug 31 19:31:55 ipfire pakfire: DOWNLOAD INFO: Host: ftp.nluug.nl
    (HTTPS) - File:
    os/Linux/distr/ipfire/pakfire2/2.25-x86_64/lists/core-list.db`
2

Sometimes this is a temporary Internet issue. Try again later.

3

Looks like your IPFire box could not resolve this hostname.

Did you check if DNS is working?

4

DNS was working for everything but ipfire related mirrors seemingly.

After disabling Pihole , i was able to refresh the update list, reenable pihole and then install 148.

This has happened before when I used to use OpenDNS rather than Cloudflare… had nothing to do with pihole. Weird

Thanks

5

Introduction:

IPFire cant update to newer versions

More Information:

Update servers cannot be located on the internet because internal name resolution is incorrectly pointing to 127.0.0.1

Resolution:

  1. Set SSH access on IPFire to allow for 15 mins

  2. Launch WinSCP and navigate to, and edit the following file by selecting it and choosing ‘edit’ from the right click context menu:

/etc/resolv.conf

  1. Change nameserver 127.0.0.1 to nameserver 8.8.8.8 and save on close editor.

  2. This has immediate effect and doesnt require a reboot

Applies to:

IPFire firewalls (ALL)

6

You will many of posts on this forum that address that those two solutions should not be used and render your DNS setup broken.

And you also, sir, have successfully disabled DNSSEC and various other features. Please check your DNS setup and do not change system configuration files unless you know what you are doing.

1 Like
7

Hi Mike can you elaborate on what is broken? Should I not use cloudflare ?

8

Peter has recently blogged about this topic:

And I wrote a couple of thoughts here:

1 Like
9

Also make sure your date and time are correct in the BIOS of your machine… login to the console and do a “date” command and then go into the bios and change the date if wrong. I had this to happen a while back and it fixed it.

Gavin