device has not been registered for pfSense+

chpalmer

Suddenly getting this on my updates page..

"Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription to receive future updates."

Is this to be expected whenever I make an interface change? Just added WAN2 for a backup internet connection.. Im well within my first year for plus..

patient0

@chpalmer said in device has not been registered for pfSense+:

Is this to be expected whenever I make an interface change?

Physically adding or removing NICs will changed the NDI and will need re-registration. It seems usually sending a PM to stephenw10 help and he can fix it.

johnpoz

@patient0 yeah @stephenw10 is normally nice enough to do that.. But you could also just open a ticket with tac. Any sort of change to the hardware would most likely change the ndi and cause that. Or if a VM adding another virtual nic, etc.

chpalmer

Thanks guys!

I didn't physically change any interfaces but just utilized one that was already there..

Getting this also in the alerts-
"Upgrade check_upgrade: "Updating repositories metadata" returned error code 1"

Then if I go to the registration tab under "System"..

"Thank you for choosing Netgate pfSense Plus

Your device does not require registration, we recognize it already. You may have already registered, or it may be a pre-registered Netgate appliance."

Seems like I broke something else along the way..

edit- and now-
"An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com )"

chpalmer

running pkg-static -d update-
pkg: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory

Hmmm..

chpalmer

If somebody running 24.11 could share their

/usr/local/etc/pkg/repos//pfSense.conf

file contents via PM I would greatly appreciate it.. I am going to try and re-write that file as it appears to be gone.

I believe there are only two lines that will be different than a 2.7.2 install.. but may be wrong..

FreeBSD: { enabled: no }

pfSense-core: {
url: "pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg",
enabled: yes
}

pfSense: {
url: "pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/local/share/pfSense/keys/pkg",
enabled: yes
}

chpalmer

@patient0 Thank you! Ive also put in a ticket to ask for an img so I can re-install if necessary..

chpalmer

According to rcoleman - https://forum.netgate.com/topic/177143/netgate-device-id-ndi/2?_=1733092672768

adding a USB interface will change the NID.. I assume then removing it will also change the ID??!?

stephenw10

Yes adding or removing any NIC, including USB, will change the NDI.

If you run pfSense-repoc -DN at the CLI it wil print the NDI actually being sent to the repo servers to check against.

chpalmer

@stephenw10 said in device has not been registered for pfSense+:

Yes adding or removing any NIC, including USB, will change the NDI.

If you run pfSense-repoc -DN at the CLI it wil print the NDI actually being sent to the repo servers to check against.

Well dag nabit! Thanks Steve! I just promised Craig I will never do such a bad thing again..

I should have been using my test box to test and not my primary.