Bug #11820
closedBackup restore problem with webConfigurator
0%
Description
Hi all,
A PFSense server that I have, had a disk problem and stopped working. For my peace of mind I have regular backup; so I did it as below:
1º I got new hardware and installed pfsense-ce 2.5.1.
2º I accessed the new PFSense and restored the backup of the pfsense that presented a problem.
3º As the interfaces were different, it was asked to set them right.
After doing the steps above, the system restarted and I realized the following problem: the port I use to access PFSense is 545/TCP (webConfigurator). The restoration brought the correct configuration but the system still remained using the standard port 443/TCP (webConfigurator). Only when I went to the configuration and clicked the save button, did the system configure port 545/TCP.
Updated by Marcos M over 3 years ago
It may be that the webconfigurator needs to be restarted after the restore. Would you be able to test again, and restart it from the console?
Updated by Marcelo Gondim over 3 years ago
Marcos Mendoza wrote:
It may be that the webconfigurator needs to be restarted after the restore. Would you be able to test again, and restart it from the console?
Hi Mendonza,
Unfortunately I have already updated all my equipment. In that case I will not be able to reproduce again. Sorry.
After I restored the configuration the system restarted. Shouldn't it have worked after restarting?
Updated by Kris Phillips over 3 years ago
Marcelo Gondim wrote:
Hi all,
A PFSense server that I have, had a disk problem and stopped working. For my peace of mind I have regular backup; so I did it as below:
1º I got new hardware and installed pfsense-ce 2.5.1.
2º I accessed the new PFSense and restored the backup of the pfsense that presented a problem.
3º As the interfaces were different, it was asked to set them right.After doing the steps above, the system restarted and I realized the following problem: the port I use to access PFSense is 545/TCP (webConfigurator). The restoration brought the correct configuration but the system still remained using the standard port 443/TCP (webConfigurator). Only when I went to the configuration and clicked the save button, did the system configure port 545/TCP.
Tested this on a fresh install. Here are my steps:
1. Installed fresh install of 2.5.1
2. Completed initial setup wizard
3. Changed TCP Port on webConfigurator to 4433 and saved config backup
4. Factory reset
5. Restored configuration file on unit
The firewall rebooted and the webConfigurator was operating on 4433 as normal.
Unable to reproduce this issue. There must be some other component to it that is failing if this is reproducible.
Updated by Jim Pingle over 3 years ago
- Status changed from New to Rejected
Rejecting for now since it cannot be reproduced. If someone can find a method capable of reproducing the problem reliably then we can reopen it.