Problemes upgrading from 2.3.4 and install of packages
-
Hello!
Our main Problem with our new pfsense-pre-installed firewall is, that we can't upgrade from v. 2.3.4 to even 2.3.5 or something. If we try to the Webinterface shows some message like " Unable to check for updates".
The problem seems to be with the repos or something:
The version would not be the worst if we somehow could install the openvpn-client-export-package! One thing before everything else, a fresh-install is more or less no option because the firewall is far far away....
I hope someone can help me out with this, thank you!
-
@linedan said in Problemes upgrading from 2.3.4 and install of packages:
somehow could install the openvpn-client-export-package!
Example : check out pfSense 2.4.5-RELEASE-p1 Now Available
As the Netgate blog already states with any pfSense upgrade : IF there is a pfSense upgrade available, install that first.
Never ever upgrade packages after a pfSense upgrade came out.As you can see in your image above, your pfSense is based on FreeBSD 10.3.
Or the repository mentions it's based on FreeBSD 11.3.
This means FreeBSD packages (for pfSense) and packages for pfSense that are pulled in are based on 11.3. They will have dependencies that won't work out.
For example, a PHP library that is compiled against FreeBSD 11.3 will not work on a FreeBSD 10.3 system. This means : the GUI will go down.So, no "openvpn-client-export-package" for you : the risk is to big.
I advise you to have the box send over to you.
Or find some one on the other side that can do a bit more as n clicking "Like" on a screen, and you guide this person.
Go for a re install, as cleaning out a system with a 'mixed identity' is possible, but very time consuming.
It also needs a great deal of knowledge of the OS.I understand that, because of the distance, you won't upgrade every time when a new pfSense versions comes out. It's ok to wait a couple of weeks or even months.
But hanging around with a 2.3.4 creates new problems. Knowledge about that version has faded out (on the forum )...I strongly advise you to look around on the forum. Others popped up with upgrade problems from 2.3.4. Some found solutions.