repository unavailable
-
Well since 2.3.x line has been EOL and no longer supported for well over a year.. why would you think there should still be repository for it?
-
Because there are still several active high availability systems running on version 2.3.x
-
Though it is EOL, the repository is still there and active, primarily to facilitate upgrading. But if you are running 64-bit, the system is trying to nudge you toward upgrading rather than staying outdated. If it's 32-bit it should still show you the latest available (EOL, out of date) items in that repository though.
-
@moisesdfelix said in repository unavailable:
Because there are still several active high availability systems running on version 2.3.x
There shouldn't be - there was plenty of notice that it was going away... There was 2 years notice given for gosh sake..
So when do you think it would be ok for it to go away - there are still freaking idiots running 1.x versions.. When does it end?
-
We deactivated the package repositories for anything <2.3 some time ago, though primarily for technical and not policy reasons at the time. We don't have a set end-of-service policy for things like that, but if some event comes along that makes it a problem to maintain, it could disappear at any time.
Unfortunately for 2.3+ you can't keep make online updates available without also having packages available since it's all in the same repository, and we do still want to encourage those who are capable of upgrading to do so. Sure, they could reinstall but that's not always easy/viable, especially when it's remote.
-
I hear ya, but users running something that have been eol for well over a year should have no expectations that there should still be support for such old versions is my point..
-
I agree that updates will be kept only in new versions, but there is no way to make available at least an extra official repository link for a possible package maintenance need even before the final update ?
-
The repository is still there, but your system is having trouble reaching it. It's on your client side, not the server side.
And there are ways to force older 64-bit clients to prefer/only read the 2.3.x repo, but it's not a practice we encourage, so we do not spread around instructions for doing it.
If it's capable of upgrading to 2.4.x, upgrade it straight to 2.4.x. There isn't a compelling reason to make a stop in between anywhere.
-
@jimp said in repository unavailable:
EOL
Ok. Is there any best practice guidance for full upgrade without backup / restore?
I can no longer see upgrade option on pfsense home screen.
-
There are links to the upgrade guide and upgrade troubleshooting docs in every release announcement, or you can go to the docs and find them as well. There are sections with information specifically about coming from 2.3.x to 2.4.x.
-
See that there is no way to upgrade by dashbord
-
Read the Upgrade Guide https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html
Follow the Upgrade Troubleshooting guide: https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html
-
All of which should of started to be looked into 2 years ago when they announced the demise of the 2.3 line.. ;) And promised then that support might only last 1 year.. That was over 2 years ago..
Your not even running the latest version of 2.3.. Sorry but I have zero sympathy for people that don't keep their security updated.. If you were on 32 bit hardware - ok, but why not 2.3.5p2 then?
-
OK, thank you for your guidance. But I think this unavailability of the package is quite recent because two weeks ago I was able to install a package using version 2.3.x
-
Again, nothing changed on the server side. If you have a problem, it's local. Something may have broken locally. The Upgrade Troubleshooting doc I linked above has suggestions to diagnose problems with package repository access.
-
I tested it on other hardware and it really seems to be some local glitch
