Unable to check for updates (SOLVED)

[stephenw10]

Interesting. It looks like at some point you added the ntop repo to get the subscription version?

[mgi]

Hello,

I have the same problem now on my Netgate 2100.

I updated the repo config already from "repo" to "firmware", but after I did that, I see cert issues related the new domain.

For some reason the content of my post is flagged as spam and I can post those. The full post can be found on https://pastebin.com/T6yRB4Yw

Any ideas?

Thanks...

[SteveITS]

@mgi The 1100/2100 repos are still offline while they sort out the issue affecting older models.
https://forum.netgate.com/topic/178049/pfsense-plus-23-01-updates-on-the-1100-and-2100-systems

[mgi]

@steveits thanks! I missed that announcement.

EDIT: seems that my box is safe when the repos are back online.

[22.05-RELEASE][admin@pfsense]/root: gpart show
=>       1  62533295  ada0  MBR  (30G)
         1    409600     1  efi  (200M)
    409601     70012     2  fat32  (34M)
    479613  62053683     3  freebsd  [active]  (30G)

=>       0  62053683  ada0s3  BSD  (30G)
         0        16          - free -  (8.0K)
        16  62053667       1  freebsd-zfs  (30G)

[frankkelly]

@rcoleman-netgate said in Unable to check for updates (SOLVED):

@peterhouse

1. Upgrades to 1100/2100 models are suspended while an issue is being fixed

This seems to be what is stopping me from upgrading a 2100 at one of my remote sites, as it has yet to be reimaged to upgrade to ZFS. I guess I will be having someone onsite walk through the reinstall process, thanks for linking that post here.

[KB8DOA]

@stephenw10 said in Unable to check for updates (SOLVED):

Interesting. It looks like at some point you added the ntop repo to get the subscription version?

Yes I did but was just a newer version as the Netgate Package of ntopng is or was quite far behind.

Now I understand the ramifications of installing outside of Official Packages.

[alexbd819]

@kb8doa Thank you sir, that did solved my issue as well!

[bavcon22]

I had the exact this problem when I decide to update my pfsense+ from version 23.01 to 23.05. On my appliance I had installed APCUPSD package and this for the reason for error on "Dashboard" page. On the "System Update" page I still receive error.

[stephenw10]

So you were able to upgrade by removing apcupsd?

[bavcon22]

@stephenw10 In web page I was not able to update, but with SSH yes.

[azdeltawye]

Hello,
Having same problem: "Unable to check for updates"

$ pkg info pfSense-upgrade

pfSense-upgrade-1.0_67
Name           : pfSense-upgrade
Version        : 1.0_67
Installed on   : Wed Jun  7 14:59:23 2023 MST
Origin         : sysutils/pfSense-upgrade
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : sysutils
Licenses       : APACHE20
Maintainer     : coreteam@pfsense.org
WWW            : https://www.pfsense.org/
Comment        : pfSense upgrade script
Annotations    :
	FreeBSD_version: 1400085
	build_timestamp: 2023-06-06T04:14:40+0000
	built_by       : poudriere-git-3.3.99.20220831
	port_checkout_unclean: no
	port_git_hash  : 33c2f885cd36
	ports_top_checkout_unclean: yes
	ports_top_git_hash: 33c2f885cd36
	repo_type      : binary
	repository     : pfSense
Flat size      : 71.0KiB
Description    :
pfSense upgrade script

WWW: https://www.pfsense.org/

Then I type in the following command:
$ pkg-static -d update

and nothing happens...

any thoughts?

Hardware: 4100-MAX running 23.05

[azdeltawye]

Additional info:

Orange LED was flashing on device indicating update was available. I then rebooted from the UI (I usually reboot prior to update) then that's when when I got the 'Unable to check for updates' message.
Subsequently, no more orange LED...

[stephenw10]

First thing to try is go to Sys > Update > Update Settings and resave the branch to the current stable version.

If it still fails try running pfSense-upgrade -d at the command line to see what the error is.

Steve

[bavcon22]

@KB8DOA When I had error like in your post I could not also get updates from github.io. I do not solve this problem yet, but in my case the suspicious program is snort. Definitely I mess up with snort's configuration to much.

[JonathanLee]

@Matt2 Make sure you hide your serial and id. This is only for you infom

[Farhan 0]

@bushman666
Thank you. This solution perfectly works for me. From 2.6.0 to 2.7.0 upgrade.