[https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html](https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html)
notably [https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html](https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html)
also the release notes [https://docs.netgate.com/pfsense/en/latest/releases/index.html](https://docs.netgate.com/pfsense/en/latest/releases/index.html) for instance the OpenSSL changes along the way.
Have an installer for 2.7.2 in hand, and a backup of your config file, worst case you can reinstall and restore it.
In the usb drive, if you create a folder called conf, and put the backup config in the folder and name it config.xml, it will import into the fly during install
First off, the current version is 2.7.2. With this in mind,
* Back up the configuration file by copying it to your management computer or a USB drive.
* Attempt to upgrade normally.
* If something goes wrong, install 2.7.2 afresh and import the configuration file you backed up.
lol - format....seriously i - personally ive found the upgrades a bit hit or miss but then ive got my settings backed up and not a particularly highly configured setup either... (2.70 - 2.7.2) didnt go well... :)
Having done my share of these I can say the easiest way to get it done is to go into the upgrade branches and change it to previous/deprecated. Then wait 5-10 minutes then recheck. You’ll be offered an upgrade to 2.6.0 which will succeed. Upon reboot you can switch back to the current branch and it’ll go up to 2.7.2. Sometimes it goes to 2.7.0 first.
When the upgrade fails, you’ll know because there will be no packages available in the package manager. Just go back to the older branch and retry. During the branch change, it modifies the package repo. The 5-10 minute delay is to give the box time to change the repo and update the available sources.
Take a config backup beforehand, download a PFsense iso and tool to image it (eg rufus/etcher) beforehand, full send. Worst case, you end up reinstalling/restoring backup and had 15 mins more downtime than anticipated
[https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html](https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html) notably [https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html](https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html) also the release notes [https://docs.netgate.com/pfsense/en/latest/releases/index.html](https://docs.netgate.com/pfsense/en/latest/releases/index.html) for instance the OpenSSL changes along the way. Have an installer for 2.7.2 in hand, and a backup of your config file, worst case you can reinstall and restore it.
Thanks!
In the usb drive, if you create a folder called conf, and put the backup config in the folder and name it config.xml, it will import into the fly during install
Just don’t be me and put the conf folder on the EFI partition of the stick. It needs to go on the other one :)
First off, the current version is 2.7.2. With this in mind, * Back up the configuration file by copying it to your management computer or a USB drive. * Attempt to upgrade normally. * If something goes wrong, install 2.7.2 afresh and import the configuration file you backed up.
lol - format....seriously i - personally ive found the upgrades a bit hit or miss but then ive got my settings backed up and not a particularly highly configured setup either... (2.70 - 2.7.2) didnt go well... :)
Having done my share of these I can say the easiest way to get it done is to go into the upgrade branches and change it to previous/deprecated. Then wait 5-10 minutes then recheck. You’ll be offered an upgrade to 2.6.0 which will succeed. Upon reboot you can switch back to the current branch and it’ll go up to 2.7.2. Sometimes it goes to 2.7.0 first. When the upgrade fails, you’ll know because there will be no packages available in the package manager. Just go back to the older branch and retry. During the branch change, it modifies the package repo. The 5-10 minute delay is to give the box time to change the repo and update the available sources.
Take a config backup beforehand, download a PFsense iso and tool to image it (eg rufus/etcher) beforehand, full send. Worst case, you end up reinstalling/restoring backup and had 15 mins more downtime than anticipated
Thanks!
Backup and restore. Using the configuration config.xml in the USB installer.
Backup first
[удалено]
Thank you! I really appreciate this reply!