no. Can follow this ticket for updates. https://redmine.pfsense.org/issues/4383

It is fixed on 2.2.x; if you are on 2.1.x then either clear your freaking cache if on Windows install the MS fonts if you are on Linux.

I remake mine every morning…  Just to be sure. (kidding - no one should be seeing that except you.  It shouldn't matter if that interface is HTTPS or HTTP in my opinion. )

@kejianshi: I would reduce my pings from every 1 second to every 5 or ten seconds in that case. Its just as useful for you and less likely to have your packets dropped as a nuisance. I did same and my apinger started behaving better. right thx.

Block access to management ports from source WLAN subnet to "This Firewall" destination. (Assuming pfS 2.2.x)

@coachmark2: Hmm… I'm running 2.2.1 and not seeing this. I know it sounds dumb, but I've done it a hundred times before... Have you gone to User Manager > Settings and changed it from Local Database to your DC on the backup firewall? Gets me every time since it's not a replicated setting that I'm aware of. Most bizarre thing, it's working now and I've literally changed nothing. And it's been broken for weeks. Just chalk it up to a gremlin?

Yeah - I hate telling people to dig into the underlying files because often you are just telling them how to break pfsense. At least if people stick to the gui newbie damage is pretty limited usually.

Awesome, that was quick  :)

Because https://github.com/pfsense/pfsense/commit/23fafd1482d7ece0614bc467a304437b516d997a

Someone else gave me this answer to a similar question: https://forum.pfsense.org/index.php?topic=88347.msg488730#msg488730 Only issue seems to be, that the line has to be added anew after each OS upgrade, or so it seems, but otherwise it does the trick for me. So the first few lines of my /etc/crontab file now look like this: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/var/log MAILTO="" #minute hour    mday    month  wday    who      command # You can easily edit the file with the Diagnostics > Edit File page.

I experienced this the other day multi wan setup did not have defualt wan switching enabled, do now its better but still not great

Thanks for the reply. Is there any way of reducing the unsuccessful logon attempts from 15 to something lower? And is it logged directly in the System - General log? EDIT: Tried some unsuccessful logons, and found out where its logged :)

PROBLEM SOLVED! I forgot that Windows doesn't want an "_" in a hostname/FQDN. I changed it to a "-" and the problem was solved.

I solved the problem. The Cert from StartSSL was botched, and since I didnt want to spend 25 bucks revoking it, I bought another from SSLs.com for 8 bucks.

Well, modifying notices files fixed my problem. Many thanks!