Pakfire update / install broken (solved)

Add-Ons
1

Hello, I have upgraded my ipfire to 2.25 core 146 at July 4th.
It looks as if pakfire is broken since this update.

I’m able to download the packages via wget without any problem. But pakfire gives an error.
I’m wondering about the HTTP 500 code, and the bad hostname “proxy.local” message in /var/log/messages. Why this?
When looking in the GUI, the proxy is not enabled.

part of messages:

Jul 21 15:46:21 ipfire-x86-64 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25-x86_64 started!
Jul 21 15:46:21 ipfire-x86-64 pakfire: MIRROR INFO: server-list.db is 1472872 seconds old. - DEBUG: force
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD STARTED: 2.25-x86_64/lists/server-list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.25-x86_64/lists/server-list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Upstream proxy: proxy.local:3128
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: 2.25-x86_64/lists/server-list.db has size of  bytes
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to proxy.local:3128 (Bad hostname 'proxy.local')
Jul 21 15:46:21 ipfire-x86-64 pakfire: Giving up: There was no chance to get the file 2.25-x86_64/lists/server-list.db from any available server. There was an error on the way. Please fix it.
Jul 21 15:46:21 ipfire-x86-64 pakfire: DB INFO: packages_list.db is 1472872 seconds old. - DEBUG: force
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD STARTED: lists/packages_list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: MIRROR INFO: 25 servers found in list
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Host: mirror.datacenter.by (HTTPS) - File: pub/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Upstream proxy: proxy.local:3128
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: pub/ipfire/pakfire2/2.25-x86_64/lists/packages_list.db has size of  bytes
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to proxy.local:3128 (Bad hostname 'proxy.local')
Jul 21 15:46:21 ipfire-x86-64 pakfire: Giving up: There was no chance to get the file lists/packages_list.db from any available server. There was an error on the way. Please fix it.
Jul 21 15:46:21 ipfire-x86-64 pakfire: CORE INFO: core-list.db is 1472870 seconds old. - DEBUG: force
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD STARTED: lists/core-list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: MIRROR INFO: 25 servers found in list
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Host: mirror.easyname.at (HTTPS) - File: ipfire/pakfire2/2.25-x86_64/lists/core-list.db
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: Upstream proxy: proxy.local:3128
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.25-x86_64/lists/core-list.db has size of  bytes
Jul 21 15:46:21 ipfire-x86-64 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can't connect to proxy.local:3128 (Bad hostname 'proxy.local')
Jul 21 15:46:21 ipfire-x86-64 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.
Jul 21 15:46:21 ipfire-x86-64 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.

Henning

2

Hi,

is there an upstream proxy configured? If yes, Pakfire will attempt to fetch
its resources by using that as well, since there is most likely no direct internet
connection available/desired.

Thanks, and best regards,
Peter Müller

3

do you have a proxy defined in your browser?

4

@Peter
Thats why I’m wondering about the messages.
There is no upstream proxy configured. As decribed: With wget on the console I can fetch every file without problems. Even pakfire gets the error.
And of course I dont know what pakfire is doing (wrong) in background.

@anon42188109
I don’t see any relationship to my browser, because all packfire commands are fired from the console.
But no again, There is no proxy defined in my browser.

5

Check you proxy config page. Pakfire take the upstream proxy from the webproxy page.

If there is no proxy before you IPFire this fields must be blank.

6

Ok, all fields are shown blank…
In my despair I changed all fields with garbage and set all possible checkboxes to “on”.
After saving the values I changed back to my inital setup.
Doing a proxy restart did the job.
Pakfire works again as expected.

Thank you.