pfSense + for Home User
-
As far as I know yes. As long as you are currently able to see the Plus pkg repos you should be able to. Since you are swapping out the SSD you will still have the old install to fall back on.
-
@stephenw10 That's my problem. I have no idea what I did with the old install. I was looking for it all morning. Never knew I would need to keep it. Also, where do I see the "Plus pkg repos"? Are they somewhere on my current install i.e. 24.11?
-
Go to System > Update > Settings to see what repo branch you're using. Then if you can see available packages in System > Packages you have access.
-
@stephenw10 said in pfSense + for Home User:
System > Update > Setting
Thanks. So here's a couple of screenshots just to double check I'm good. (Thanks for your help)
-
Yes, looks good. You would be seeing errors there otherwise.
-
@stephenw10 Many thanks stephenw10
-
@FrankZappa Sorry to be a pain, but those screenshots are from my current install on the failing SSD. The screenshots are NOT from the new SSD, which I have yet to install pfSense on.
-
Yes. But since the NDI will remain the same the net installer should validate it and allow installing 24.11 directly.
-
@stephenw10 Thank You Sir. Really appreciate the help.
-
@FrankZappa This is just a follow-up on this thread. Stephenw10 is spot on. I installed pfSense on a brand new SSD (the same computer). It asked if I wanted 24.11. I said yes, and all is right with the world. My Netgate ID is registered, and I still have pfSense +. I'm pretty happy. The only thing that didn't work on the new SSD is OpenVPN. I'm not sure why the config settings are a problem. Also, many of my previous packages did not install. No problem, I reinstalled them. Regardless, my pfSense + license is still good (until Netgate removes me). Thanks stephenw10. I would have gone down an entirely different, more complicated path if not for you.
-
@FrankZappa said in pfSense + for Home User:
many of my previous packages did not install.
If you've used the config.xml from the old system, all the package info should be in there. If the packages were not present (installed) on the new system, but referenced as installed in the imported config file, the new pfSense will auto install them.
IRC, this will happen in the back ground, and while this is ongoing, a banner will mention this on the dashboard (not sure).If packages still didn't come over, its 'look at the logs and your imported config file' time.
After all, if parts of the info didn't came over it's pretty clear that you don't have the entire list of the "what didn't make it".
Parts of what OpenVPN needs, like certificates and defined OpenVPN users could be one of them. -
I have sometimes needed to restore a config twice to get the packages. Usually when a config requires something significantly different on WAN to get connectivity so fails the first time around. You can just manually install the packages but often simply restoring the config again is easier.
