pfSense CE auto upgrade

stephenw10

Hmm, what error do you see at the CLI from?: pfSense-upgrade -dc

n1md4

[2.6.0-RELEASE][root@sharevdi.home.lan]/root: pfSense-upgrade -dc 
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Your system is up to date

So why is the GUI not responding in like. GUI says "unable to check for updates".

stephenw10

Good question, since it uses the same code.

Can you see the list of available packages in the package manager?

n1md4

@stephenw10 Yes, there are available packages. The install list is empty, but that's expected. GUI bug ...

stephenw10

Hmm, what about in System > Update? If it shows the package list it should be able to see updates.

n1md4

@stephenw10 Both System -> Update and dashboard updates are not working. Just says "Unable to check for updates".

Is this the latest version:

2.6.0-RELEASE (amd64)
built on Mon Jan 31 19:57:53 UTC 2022
FreeBSD 12.3-STABLE

rcoleman-netgate

@n1md4 Yes, 2.7 is currently in development

n1md4

@rcoleman-netgate so no known reports of the system upgrades working on the command line but not the GUI?

stephenw10

Not in 2.6.

Try running pkg upgrade and see if it offers you any updates.

n1md4

@stephenw10

Output below:

[2.6.0-RELEASE][root@sharevdi.home.lan]/root: time pkg upgrade
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (2 candidates): 100%
Processing candidates (2 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
0.149u 0.033s 7:34.66 0.0%      2622+230k 25+40io 12pf+0w

Any ideas why it takes forever to update too?

stephenw10

7.5 mins?! Mmm that should be a few seconds. Does it stop at any particular point?

jimp

Sounds like what might happen if it's struggling to connect over IPv6 and failing, waiting for each thing to fail on IPv6 before falling back to IPv4. Might try toggling the option to prefer IPv4 over IPv6 for the firewall itself (System > Advanced, Networking tab).

n1md4

@jimp thanks. This was indeed the issue. Switched to prefer IPv4 and everything is now working; updates and upgrades take seconds not minutes, and the GUI now displays updated status too.