Updated from 22.05 to 23.01 and now it says it's not registered.
-
Everything went fine but now it says its not registered.
Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription at the Netgate store to receive future updates.
Harley
-
@hpeters63 You have to register again. Maybe your old token still works.
-
Already tried to register using the old token didn't work.
-
@hpeters63 If you hardware has changed anytime after the first registration, now you pay the bill.
Or get another free token, if your qualified. -
@hpeters63
I had the same problem. i'm on NetGate equipment. I reached out to TAC and after poking a while, they assured me that in my case anyway, the equipment is showing as registered on their side, but that there was a problem on their end that would, when resolved, eventually show the device as registered.
There wasn't a lot of clarity on the timeline for that last part, but it hasn't happened in the last 24 hours and it still shows as requiring registration.
Time will tell. -
Thanks for the info.
I'm in no hurry everything works and there's nothing to upgrade to anyway.
This is just a kvm virtual machine i use as my backup router. It's configured the same way the main router is so i update it first and if everything goes well then i try updating the main router. -
@hpeters63 This just happened to me last night. Our home pfSense Plus router (bare metal Dell OptiPlex 3050 with a Home license) upgraded to 23.01fine but then the "Your device has not been registered for pfsense+..." message appeared and Updates were disabled.
In my case the original installation NIC went bad so I had to replace it while running 22.05 with no issues. After some late night researching it seems the Netgate Device ID (NDI) hash is derived from the NIC MAC address and a string somewhere from the motherboard. So... when I had to replace the NIC it changed the NDI hash but pfSense+ did not seem to notice/complain until the 23.01 update/upgrade. It also seems NIC changes in a virtualized pfSense+ environment may also change the NDI hash. I understand RAM, CPU, and drive changes may not change the NDI, but someone please correct me if I'm mistaken on that. Again, it was late night researching so...
Reinstalling the original NIC may get the original installation NDI hash back (maybe???)... but since that NIC is dead it won't solve my issue. I just went to System - Boot Environments and activated the 22.05 backed up environment for now. Home and Lab licenses don't include any TAC support and I guess one can request a new pfSense+ token with another order... but I wonder if there is any way to update my existing license order/account with the new NDI?
-
@knuckles Contact TAC support.
-
@michmoor Thx for the reply but as I understand it... pfSense+ Home and Lab non-commercial use licenses do not have TAC support. "Full access to pfSense Plus documentation and technical assistance via Netgate user forum"
The TAC support ticket entry page lists support levels of TAC Lite, Pro, Enterprise... none of which apply to Home/Lab licenses. Will they respond?
-
@knuckles you can still contact TAC to get the registration sorted out.
-
Has anyone actually tried to get to tac support?
https://www.netgate.com/tac-support-requestWhen i go there it shows in bold letters:
Support Ticket Request FormBut there is no form:(
-
@hpeters63
work yesterday when I reached out to them as noted in this thread above.
also just checked and I see the form the link you shared.
-
Ok thanks for checking.
I am running pfBlockerNG and it was blocking js.hsforms.net whitelisted it and i now see the form.
-
Ok well that turned out to be a mess.
After getting the key reset i ended up with the following error.
Your TAC Subscription expired on 2023-02-17 14:26:00+00:00. Please renew your TAC Subscription or purchase a pfSense+ subscription by visiting the Netgate store.
I know what happened when I contacted tac support they had a couple of follow up requests and another tech had taken over before resetting the key. The first tech knew it was a free key but i suspect the second just assumed it was a paid tac support version.
Fortunately it is a virtual machine so just modified the mac addresses by one digit to generate a new NDI number and ordered an new key.
Just ordering a new key is what i would recommend everyone else do.
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
If you send me your NDI in chat I can look into it. If t changed though you should just be able to reregister it using a new token.
Steve
-
Sent you a chat message
-
I recently replaced my NIC and I am now experiencing this issue. I have been using Pfsense+ for several years. Is it still possible to get a new token?
-
Send me you NDI and order number in chat and I'll check it.
-
@stephenw10 said in Updated from 22.05 to 23.01 and now it says it's not registered.:
Send me you NDI and order number in chat and I'll check it.
Sorry, but how can I PM you? I can't find the PM button any more.
EDIT: found it. Message sent. -
@frodo
Thank you Netgate! Working now :-)
