• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

23.01.b.20221217.1429 Your device has not been registered for pfSense+

Plus 23.01 Development Snapshots (Retired)
19
61
9.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    stephenw10 Netgate Administrator
    last edited by Dec 19, 2022, 11:32 PM

    There was a backend issue that could have caused that. Are you still seeing that message?

    R 1 Reply Last reply Dec 20, 2022, 1:46 PM Reply Quote 0
    • B
      Bob.Dig LAYER 8 @rpotter28
      last edited by Dec 20, 2022, 7:59 AM

      @rpotter28 Maybe you can tell. Reverting back to stable and that problem was gone for me.

      R 1 Reply Last reply Dec 21, 2022, 12:59 AM Reply Quote 0
      • R
        rpotter28 @stephenw10
        last edited by Dec 20, 2022, 1:46 PM

        @stephenw10 said in 23.01.b.20221217.1429 Your device has not been registered for pfSense+:

        There was a backend issue that could have caused that. Are you still seeing that message?

        Hi Stephen, yes as of 23.01.b.20221217.1429 I still see the message.

        Also In the update settings there is no branch select able, on both tabs there is no branch shown.

        1 Reply Last reply Reply Quote 0
        • S
          stephenw10 Netgate Administrator
          last edited by stephenw10 Dec 20, 2022, 11:52 PM Dec 20, 2022, 11:38 PM

          @rpotter28 and I looked into this and it looks like the NDI has changed which is why the message was sent.

          Steve

          B 1 Reply Last reply Dec 21, 2022, 9:22 AM Reply Quote 0
          • R
            rpotter28 @Bob.Dig
            last edited by Dec 21, 2022, 12:59 AM

            @bob-dig said in 23.01.b.20221217.1429 Your device has not been registered for pfSense+:

            @rpotter28 Maybe you can tell. Reverting back to stable and that problem was gone for me.

            @Bob-Dig this has been fully resolved for me. Thank you @stephenw10.

            I will leave it up to him to explain.

            1 Reply Last reply Reply Quote 0
            • B
              Bob.Dig LAYER 8 @stephenw10
              last edited by Dec 21, 2022, 9:22 AM

              @stephenw10 said in 23.01.b.20221217.1429 Your device has not been registered for pfSense+:

              it looks like the NDI has changed

              What is a NDI? The Netgate ID of my hardware? 😰

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Dec 21, 2022, 1:06 PM

                Yes. In @rpotter28's case t had changed and hence the server was sending that message to the new, unrecognised, NDI.
                If your NDI has also changed the same thing would happen. If you PM me your NDI I can check it.

                Steve

                B V 3 Replies Last reply Dec 21, 2022, 1:19 PM Reply Quote 0
                • B
                  Bob.Dig LAYER 8 @stephenw10
                  last edited by Bob.Dig Dec 21, 2022, 1:23 PM Dec 21, 2022, 1:19 PM

                  @stephenw10 said in 23.01.b.20221217.1429 Your device has not been registered for pfSense+:

                  If you PM me your NDI I can check it.

                  I restored an image to be back on stable and I am "genuine" 😉 again, so there is probably nothing to see right now. But I copied it now and will check when I test the beta again, thanks.

                  1 Reply Last reply Reply Quote 1
                  • B
                    Bob.Dig LAYER 8 @stephenw10
                    last edited by Bob.Dig Dec 23, 2022, 11:24 AM Dec 23, 2022, 8:15 AM

                    @stephenw10 Being on 23.01.b.20221221.1946 and problem persists. According to the dashboard, my Netgate Device ID hasn't changed to before.

                    login-to-view

                    Same with 23.01.b.20221223.0600

                    login-to-view

                    If I should guess, I changed my CPU of my vm-host some weeks ago and pfSense+ probably didn't flagged me as non-genuine but with every "upgrade" it does.(?) Although ID still hasn't changed to right before the "upgrade".

                    1 Reply Last reply Reply Quote 0
                    • V
                      Viper_Rus
                      last edited by Dec 25, 2022, 10:07 AM

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • V
                        Viper_Rus @Bob.Dig
                        last edited by Dec 25, 2022, 10:10 AM

                        @bob-dig

                        What is the theme that is on the screenshots in the first message? Very nice

                        B 1 Reply Last reply Dec 25, 2022, 10:11 AM Reply Quote 0
                        • B
                          Bob.Dig LAYER 8 @Viper_Rus
                          last edited by Bob.Dig Dec 25, 2022, 10:12 AM Dec 25, 2022, 10:11 AM

                          @viper_rus said in 23.01.b.20221217.1429 Your device has not been registered for pfSense+:

                          What is the theme that is on the screenshots in the first message? Very nice

                          https://github.com/darkreader/darkreader
                          😉

                          1 Reply Last reply Reply Quote 1
                          • V
                            Viper_Rus @stephenw10
                            last edited by Viper_Rus Dec 25, 2022, 11:30 AM Dec 25, 2022, 11:28 AM

                            @stephenw10

                            The same message popped up. pfSense is set to proxmox, I don't know if Netgate ID has changed, experimented a lot with machine tuning.
                            How can I solve this problem if the NDI has changed?
                            Is it possible to re-enter new the license code ?

                            I wrote my NDI in private messages.

                            login-to-view

                            1 Reply Last reply Reply Quote 0
                            • S
                              stephenw10 Netgate Administrator
                              last edited by Dec 26, 2022, 1:08 AM

                              Replied in PM. But probably the NDI is not what was registered originally. We are going to need a method to resolve that situation, I can see it's going to happen relatively often. I have brought it up with our developers.

                              Steve

                              1 Reply Last reply Reply Quote 2
                              • C
                                chickendog
                                last edited by Jan 4, 2023, 10:21 AM

                                Confirming I've got this exact message too.
                                Upgraded from 22.05 to 23.01.b.20230104.0600

                                I made no changes to the hardware since I upgraded from pfSense CE 2.6 to 22.01 then to 22.05. So not sure how the NDI would've changed.
                                It is installed on a VM though.

                                @stephenw10 Is there anything you can do in the backend to restore it if I PM you my NDI? Thanks

                                1 Reply Last reply Reply Quote 0
                                • S
                                  stephenw10 Netgate Administrator
                                  last edited by Jan 4, 2023, 12:29 PM

                                  There may not be if you made no changes. That would be very odd though. We can check what it's seeing if you PM the NDI to me though.

                                  Steve

                                  C 1 Reply Last reply Jan 4, 2023, 12:59 PM Reply Quote 0
                                  • C
                                    chickendog @stephenw10
                                    last edited by Jan 4, 2023, 12:59 PM

                                    Thanks @stephenw10 just PM'd you.
                                    On second thought I did muck around with passing through NICs. But I reverted the changes since it didn't work for me. Maybe that triggered it though.

                                    1 Reply Last reply Reply Quote 0
                                    • V
                                      Viper_Rus
                                      last edited by Jan 4, 2023, 11:16 PM

                                      I fixed the situation like this:

                                      Created a new pfsense 2.6 virtual machine with the same set of network cards and MAC addresses as the main machine. NDI matched. Received a new activation code plus on the netgate website and activated a new virtual machine. After that, on my main pfsense installation, the error message disappeared

                                      C 1 Reply Last reply Jan 4, 2023, 11:25 PM Reply Quote 0
                                      • C
                                        chickendog @Viper_Rus
                                        last edited by Jan 4, 2023, 11:25 PM

                                        @viper_rus Ah I see, thanks for that. I might try that if Steve can't fix it for me.
                                        Annoying that there isn't just a Register section in 23.01. It's missing!

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          stephenw10 Netgate Administrator
                                          last edited by Jan 4, 2023, 11:45 PM

                                          Yes, it's something I raised last week we are looking into the best solution.

                                          C B 2 Replies Last reply Jan 4, 2023, 11:59 PM Reply Quote 1
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.