Thanks for finding this. The separator text is now wrapped in a CDATA block before being saved and you sample sequence now works as expected.

When I set that it puts the zero line in the middle.  Allowing for negative users.  Number of users can never be negative.

I had one of my pfBlockerNG beta testers run into this issue, when UBlock was blocking a FA icon. Info here: https://github.com/chrisaljoudi/uBlock/issues/428 https://github.com/gorhill/uBlock/issues/15

Thanks for the feedback. We might find a better solution for mobile nav in the future.

Is pfSense doing a DNS query for my.local.domain.com? Do you have SOA for my.local.domain.com?

Just a suggestion, no idea if this will work. Try two backslashes '\' or three '\' or four '\\' it might be escapable.

All other than jdillard look here for more info https://forum.pfsense.org/index.php?topic=109728.msg611527#msg611527

Is you blocking private networks and loopback addresses on wan interface? http://<pfsenseboxlanip>/interfaces.php?if=wan https://<pfsenseboxlanip>/interfaces.php?if=wan And NAT rules http://<pfsenseboxlanip>/firewall_nat.php https://<pfsenseboxlanip>/firewall_nat.php [image: Screenshot_22.png] [image: Screenshot_22.png_thumb] [image: Screenshot_23.png] [image: Screenshot_23.png_thumb]</pfsenseboxlanip></pfsenseboxlanip></pfsenseboxlanip></pfsenseboxlanip>

@johnpoz: Shouldn't this be in the capt obvious section? ;) Probably but I've only installed few certs. I'd never been prompted for a PEM pass before and didn't understand the ramifications. Besides, posting the obvious may lead to fewer newbies bugging you about it.

@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?