@NOYB:

The Beta theme selections includes /usr/local/www/css/pfSense-BETA.css (or pfSense-dark-BETA.css).
You can put your own experimental css in those to tailor the GUI as you like.

It's more a place for experimental CSS in pfSense itself. It came into being when a lot of changes were flying to the ALPHA version. So, in theory (as some changes require more than just CSS to implement), someone could put a (more radical design) idea in that file and say "Hey, check out the BETA file and let me know what you guys think" and build on it further based on the feedback or if people like it, then merge into the main CSS.

If someone wants to make their own override file they should create a similar file in the same directory with a different name, otherwise it might get overridden in a future release.

Its in the system log / openvpn you can see I just connected with 1.2

Apr 7 14:20:17 openvpn 43383 xxx.xxx.237.38:51182 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA

I'm not using "2.3".

If this https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/widgets/widgets/captive_portal_status.widget.php#L96 IS 2.3, then the (small !) bug is definitely there.

Opening a ticket on redmine without actually using the version 2.3 where I post a ticket for, euh, noop, sorry.

Knowing it's a really minor issue, it can wait (when I shift to 2.3 beta …).

..apparently yes:

https://forum.pfsense.org/index.php?topic=108082.0

Check 'sysctl dev.em' or dev.igb depending on whether that's an em or igb NIC, that'll show the specific error counter.

Unfortunately same problem here, same version.

It happened after upgrading from version 2.2.4 through a new install using a restored config.xml.

How can I bypass these Welcome screen?

Deactivate the DHCP server at the ISP router, then set up a static WAN IP address at the pfSense box, and let
only the DHCP server from the pfSense working, not vice versa, please! And the bridge port option should be
not used by you it often coming besides with other problems.
Route where you can and bridge only if you must.

I have a similar set up without any kind of problems reaching the devices in front of the pfSense and behind
of them and on top also both WebGui interfaces of the both routing units. The double NAT will only "eat"
3% - 5% of the entire throughput, pending on the power your hardware.

In my eyes your problem will be pointed to the both DHCP servers each in one network and the bridged port
nothing else.

@andersons:

Hi all! I was running some tests on squid when after a reboot, the webGUI access has been broken. The message that i get now when i try to access is:
Fatal error: Call to undefined function gettext() in /etc/inc/priv.defs.inc on line 10
Any help? Thanks,

Yes.
http://php.net/manual/en/function.gettext.php
So, a build in (PHP) function isn't there anymore ….
Consider your box very broken.

@Gertjan:

Web GUI on WAN == major security flaw.
Try contacting web gui on LAN.
Check if it is running (suing direct screen / keyboard access) or SSH acces.
Restart it using option 11 and/or 16.

Thanks for the reply.  If you look at my original post I stated:

but the WebGUI will not load from the LAN.

Also, tried option 11 and 16 as well as rebooted the entire system but that did not work.  I assume the process of the WebGUI is named: lighttpd in order to check if it is running?

Without more detail from the OP it's impossible to know if yours is related in any way, you should start a fresh thread for that rather than using this (potentially unrelated) one.

Figured it out.  By default, IE 11 runs any intranet sites in Compatibility mode.  To fix, click the Settings gear in the top-right corner.  Select Compatibility View settings.  Uncheck Display intranet sites in Compatibility View.  The page will immediately refresh and the graphs are now visible.

Edit:  I suspect that this only applies if you have something in Control Panel - Internet Options - Connections - LAN Settings - Advanced - Exceptions, with Bypass proxy server for local addresses checked.

Yes, with this background I think you are right. When an intruder is on my firewall, the CA isn't very valuable any longer and the CA is only used for my own services.

But who knows what exotic scenarios someone needs to do something. So for me it's ok not store it on my pfSense, regardless that it is not really more secure  ;)

And with this one of my dozen unused USB sticks lying around is now in use again  :)

Edit the source, add it around here:

https://github.com/pfsense/pfsense/blob/RELENG_2_2/usr/local/www/guiconfig.inc#L55

@jimp:

2.3 does now have a hit counter on the rules view, though it was reworked a bit in the process.

Great!

Congrats for all! ;-)

[]`s
Jack

re-installing the PHP might fix this issue.