Help, strange problem after upgrade to 2.5

[Guest]

[Herbertlee]

Hi, I am running 2.4 before and I backup just the setting and import it to 2.5. Everything work fine the first  hours, I can reboot and logon to admin-interface and edit setting. And  the system will remain up in the next 24 hours but I am not able to logon to the admin-interface anymore through . . :10443/  

The firewall and VPN is still up and running but if I try logon to admin-interface after serval hours,
page will take long time to load then then return with an error "page not found". I reset to default and still not able to logon to the admin interface. The only thing I can do is reinstall the firewall but get the same result. What am I missing?  

[steve.goos]

when you can get in, enable ssh access.

then use terminal or from windows... umm putty works.

login and reset the web services. it could just be hung up. then when you get in check the logs. if not sure. find the system logs and can post them here once you have reviewed them for any sensitive information.

[Herbertlee]

Hi, any one know what is the root's password to login to the Shell Console for EFW 2.5?
1) I press 0 and it display
    firewall:
2) I then enter "login" and it prompt for
    root password:
3) I tried root / admin / endian with no luck.

[trymes]

You set the root password when you completed the initial setup of the machine via the web interface. Chances are you made it the same as your admin password for the GUI, but perhaps you used something else?

Tom

[mrkroket]

There is a way to change the root password, by editing the boot process and starting Linux in single user mode.

I don't trust using a backup from earlier versions on the new ones. It can break something.
The best way is to create a backup in 2.4.
Then install on the new machine the  Endian v2.5. Configure the basic stuff, network and so.
Create a backup in 2.5. This backup will be the template of you backup/migration.

Open both zip archives, search useful files and check their structure between versions.
If everything is similar (same columns, same data type), then you manually replace only those files on the 2.5 backup.
If some files are not similar but you might use the info on 2.4 to create a file of the 2.5 version, do it.
It's a hard and slow process, but you ensure that nothing wrong happens when migrating from older versions.

[qhris]

I have never had success upgrading; too many odd results. You are better off doing a fresh install and recreating your rules from scratch. It's a PITB, but it saves hours of frustration.
Q