2.4.1 Package Manager Unable to retrieve package information
-
I'm not sure if I have the exact same issue or not.
I successfully upgraded to 2.4.2, and now I can't reinstall packages because when I look at the Available Packages page nothing comes up.
I don't get any errors either. The installed packages page works fine.
Any thoughts? -
I install pfsense with 2.4.2 and then push the backup file.
Packets now work properly again ;D
I think the problem had to come from 2.4.1
-
"pkg upgrade pkg" command fixed it for me… read on...
I upgraded from 2.3.x to 2.4.2_1 (multi stage upgrade and had to jump through a few hoops). I had the exact same issue with not being able to retrieve package info. Everything I found online didn't work (DNS, option 13 at console/ssh, pkg update command...). Eventually I found a post on some site that said to run "pkg update" and then "pkg upgrade pkg". I'm not linking the site because it contains content that drove my Norton Anti-Virus crazy. As soon as I ran "pkg upgrade pkg" at the console, I refreshed the 'Installed Packages' page and bam... fixed.
-
hi anyone can help me please my pfsense 2.4.2
i can't install any package
i try "pkg upgrade pkg"
but dos't working :( :( :(
-
hi anyone can help me please my pfsense 2.4.2
i can't install any package
i try "pkg upgrade pkg"
but dos't working :( :( :(Fix your connectivity (WAN, default gateway) and/or fix your DNS resolution. The firewall itself cannot reach DNS servers to resolve a hostname.
-
In order to fix this problem, asuming that yours internet connection is working, you only need to fix the clock changing the host value in your NTP's client settings according to your region or country in the admin panel.
And then you can successfully update your pkg repositories within the shell:
pkg update
pkg upgrade -
okay so I spent quite a bit of time investigating (version 2.4.2) why I cannot install a single package. I checked most of the options mentioned above, but in my case the problem was hidden in System > Routing > Gateways .... both on LAN and WAN interface settings the Default Gateway check box was checked...that is why all the DNS calls went out via the LAN GW and not out to the internet. Once I unchecked the box for LAN interface, all worked like a charm. There can only be one default gateway, rest has to be fixed with static routing!
-
So, why do you have a gateway on your LAN interface?
-
@grimson we route management traffic via LAN (in this case transfer / DMZNet vlan, with a next hop on the other side, hence the dedicated GW on that interface) and the rest via WAN with its default gateway. I do not want to discuss my network topology here. I just hope that my post can save someone's time and frustration I went through. I guess it would be a nice feature to "limit" the option to have more than one default gateway selected as this caused the problem in the first place.
-
@tonylopez1023
[2.4.5-RELEASE][admin@mypfsense.local.lan]/root: pkg update
Updating pfSense-core repository catalogue...
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!my brand new 1100... unpacked it today. Package manager is not working at all :-(
-
@ericatnetgate Please open a ticket at https://www.netgate.com/tac-support-request to request the current firmware!
