Will do. Many thanks

I re-installed, this time using the default kernel rather than the embedded kernel.  Everything works fine.  The webgui comes right up. The embedded kernel and my hardware dont seem to get along.

pfSense automatically listens for connections to the settings page from all interfaces, but only opens the firewall by default on the LAN interface (you can disable the "anti-lockout" rule in settings, but be careful). If you wanted to access the settings page from the WAN, for example, just add a rule to the WAN to allow access from anywhere to the WAN IP address, protocol HTTPS (port 443) TCP, and you will be able to access it remotely. Same is true of any other interface, add a similar rule for access to the interface IP, from any or specific IPs as desired. Or, add explicit block rules if you want to or if you've opened it up with other rules. I also tend to change the listening port to something other than 443 so I don't interfere with port-forwarding of HTTPS and am on a non-standard port (less likely to be target of random scans from Internet or guesses internally).

Well, I tried it and the outcome is documented here: http://forum.pfsense.org/index.php/topic,41193.0.html Learn from my fail. (ok, not a total fail, as I did have a config backup and fresh install image on hand for a quick recovery. Learn from my example  :). Of course I don't know for sure that flashing a vga image caused the problem, but it's the only obvious hypothesis from my POV.

The same config worked on the same hardware right before the update. It also worked on the same hardware after doing a clean install of 2.0-RELEASE. The only obvious thing that changed besides the date of the build was that I flashed a vga-enabled image on a non-vga box.

You should be able to upgrade that way, but backups are always ideal.

There isn't a cleanup guide. It shouldn't be necessary. Though apparently that case wasn't handled by the upgrade code. You could install the cron package and remove the old job that way. I opened a ticket for the upgrade bug: http://redmine.pfsense.org/issues/1905

@Rural: (…) That was the problem. Fixed that. (...) Nice to hear. :)

@LostInIgnorance: Some of the old code that worked with IE may have remained in the firewall or in your browser history, but on a fresh install, that all would be deleted. Thank You that helps clear this up.

I'm seeing the same problem with the final release under VirtualBox. It doesn't happen with the x86 version, so trying that may help you too. Later, when I have time, I'll try to troubleshoot the problem.

Thanks Havoc

THANKS, I think I can sort it now!

Ok, clear now. Thanks a lot for your prompt answer !

I have found some problems upgrading from RC3 to 2.0 RELEASE too. NRPEv2 configuration is lost (this happened upgrading from rc1 to rc3 too) Squidguard in transparent mode stops working, now i only see on access logs  TCP_DENIED/400 2260 GET NONE:// - NONE/- text/html and a invalid petition error on browser. Seems something isnt working properly on http traffic redirection. Thanks and best regards.

Is the same one CF card ,It can bootup in the IBM X306m ,But can't boot in the X305

Of course, there is plenty of documentation and even FAQ articles.