Removing all of the old certs is what helped, not the full reset, but the full reset removed them. After you access a few more pfSense installs it will break again until they fix the bug.

hahaha had this one today, so i did the following: typed https://this.is.my.wall:443/system.php and changed theme to nervecenter.

hahaha had this one today, so i did the following: typed https://this.is.my.wall:443/system.php and changed theme to nervecenter.

Not currently, no. You can review the changes manually under Diagnostics > Backup/Restore on the Config History tab

Not without rewriting the code, I suspect.  There are other monitoring packages available that may give you what you want.  Look into bandwidthd, darkstat, ntop, ntopng for starters.

I found some code that may work see below: <virtualhost *:80="">ServerName undesired.example.com   ServerAlias example.com notthis.example.com   Redirect / http://www.example.com/</virtualhost> <virtualhost *:80="">ServerName www.example.com</virtualhost> I found this code on http://stackoverflow.com/questions/3028166/how-do-i-redirect-a-user-using-apache-rewrite-to-the-fully-qualified-domain-nam My question before I attempt to add this is what web server does PfSense use 2.1.5 64 bit and what web server does 2.2 64 bit use? I'm assuming that it is Apache but you know how the saying goes. I would like to see functionality built into PfSense in the form of a check box maybe on the Advance tab. If I have some time I may try to hack this in this weekend. Doesn't seem like to many lines of code to add.

Ok this worked as intended, but with a side effect, now I'm never redirected to https, the idea was to redirect only if the "sgerror" was on the url, but now I have to explicitly put https to go to https on my webconfiguration. This is better than nothing, but if it were only to url's with "sgerror" on the string it would be perfect. Something wrong with my RegEx pattern? Best Regards

Gotcha, thanks!

Would the format of the Snort/Suricata Alerts Tab be a reasonable Format to follow? It wouldn't be too hard to mimic that layout for the States Table.

-rw-r–r--  1 root  _dhcp  867k Oct 22 14:16 dhcpd.leases -rw-r--r--  1 dhcpd  _dhcp  2.4M Oct 22 14:04 dhcpd.leases~ I guess thats not that big, right ?

I found the delay was actually coming from the browser, not the pfSense box.  By removing the exceptions for the self signed certificates in the browser, and re-accepting them, all is good now and pfSense GUI is back to running fast.  I'll keep an eye on it and post if anything comes up. This is an issue from Firefox 31 (I guess you were using Firefox). There are other threads about this also. In Options, Security you have to View Certificates and delete all the ones listed under "Company Name" - those are the "unknown" ones that you have previously added as exceptions in the past. Then things speed up again.

Great, yes this fixed the problem. I removed one dollar sign and now it is working again. Thank you!

Same here - tried Firefox and Opera. /usr/local/www/diag_dns.php is the culprit. The version from 2.1 branch on Jun 17 works: https://github.com/pfsense/pfsense/commit/ee4ba9fba1f9d49396f3a4882a3239a83c5036d6 Later versions have had support for $GET changed and then removed. So it no longer works for diag_dns.php to be directly called like it is in the Firewall Log Widget. My guess is that this functionality has to also be removed from this Firewall Log dashboard widget. Redmine issue raised: https://redmine.pfsense.org/issues/3904

Every time I do a gitsync, I have to re-apply the patch. I haven't any issues using firebox on windows 7.

It would take a little bit more work to sort it out to use the full width, but should be 'doable'.

Install the widescreen patch or lower your font size. https://forum.pfsense.org/index.php?topic=81167.0

Anyone?

I had the same issues after a fresh setup (cf card died). The system was just booting and starting up webConfigurator fine (factory default config). But after I restored from my config.xml the service did not come up automatically anymore. I traced it back to the fact, that I was restoring a config.xml that was running on a full installation to an embedded installation… maybe that applies to you as well.