EFW Support

Just installed 2.3 and restored a backup from 2.2.  Now the web admin no longer works.   Gives this error.



Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


Anyone else having an issue?

Thought i'd post some more info,  apparently if you do not restore from a backup the web front end works fine.  However once you restore your backup it ceases to work again.  Not sure what the issue is, may have to reinstall 2.2 till I can figure it out.

same issue here.

had to completely reinstall 2.3 again.

 ::)

Did your backup work after reinstalling 2.3?  Mine still didn't, i had to go back to 2.2 for the time being

i didnt even try.. just set it up by hand.

Yeah mine worked before I reloaded the backup settings.  I could just go in and set it up by hand but I don't really feel like it.  I may mess with it some this weekend

Hi Guys,

I think I have uncovered the problem, well found a solution.
It looks like one of the web script files to show new Dashboard has a different name to before, and restoring from a backup confuses it.

Login via console and run the following
cp /var/efw/h**eader.pl /var/efw/h**eader23.pl (Remove the **s, as the forum wont allow posing of the word hea d )


That fixed it for me, and all seems to be functioning correctly!

Hope this helps someone!
Jim

I guess I spoke too soon!
It appears to have fixed it enough to see the dashboard and perform all of the old functions, i.e. the ones with the same webmin pages as in 2.2, but it struggles with the new ones!

Jim

I can't believe that we are the only 2 having this issue

no your not the only two...make that 3 now that i posted to this thread  :)

i will try the fix later this week and post my results.

any luck?

I got the same problem . Used a backup from 2.2 rc3 . Unable to log on the web admin :( ...

Would be real nice not to start from scratch again .. Anyone ?

Tried every way I could think of and still no luck

Add me to the list. I was going crazy. And I have to many personalized static IPs and firewall rules to do it all over by hand again. I've gone through the same steps of the rest of you. My 2.3RC1 version works fine up until I restore my backup from 2.2. No matter the restarts after the initial setup or whatever. I'm not a Linux guru or I might go playing with the code, but I wouldn't know where to start.

I wonder if there will be a convert tool, when 2.3 goes stable, for us using an older version?

Ok,

So I've had a little more time to look at this now, and I have moved a few files into my backup from 2.2, and all seems to be ok so far (i've been using it for 2 days, with the web interface working!)

Here's what I did, if you try it, let me know how it goes for you!!

 - Backup 2.2 (for the sake of this I'll call this archive 22.tar.gz)
 - Install 2.3rc, and go through the basic installation
 - After reboot, make a backup of 2.3 and download the archive (again I'll call it 23.tar.gz)
 - Extract the 23.tar.gz somewhere convenient (I was on Ubuntu so just used archive manager) I think 7-zip will do it on windows, but ill confirm later, as I dont have  access to windows atm.
 - Then open 22.tar.gz, and add the following files from 23.tar.gz:-
      - /etc/endian/emi.conf (you will need to create the endian folder in the archive)
      - /var/efw/header23.pl
 - Restore the modified 22.tar.gz to your server running 2.3rc

I hope that makes sense, I probably made it look really confusing, but its just copying 2 files from one archive to another.

Thanks Rizzlar !

But their is still some "flaws" , my smtp blacklist/whitelist settings are not showing , although they work... ( I confirmed they work by the new smtp live log :) ).

UPDATE : Actually, if you make a new entry on the black/white list , the old settings are erased .

------

I presume its because the format of  the configuration files has changed or something, and short of comparing every single file between the two backups, there isn't much we can do.

I will have a little play around with the files later this week.
I think we might just have to wait until they come up with a converter/import tool for this, as those guys know exactly what they changed.

rm /var/cache/menu/*.json
fix it