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

Figured it out, will need to do some re-coding

I see this post seems to be related to my cause. Very helpful info.  I can see from his code that int= is the interval rate. I do see the authentication problem is more work than implementing the graph.

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

sample code:
http://pf.sense.ip/_graph.php?ifnum=wan&ifname=WAN&timeint=10

Noticed the widget breaking a couple of days ago. Gonna try out your solution.

I can confirm that turning off device polling fixed it, thermal widget workes as expected now.  Explains why loading a config showed the issue, device polling is off be default, config kept turning it back on.

Also a positive, my CPU would hover idle right around 13-15% load, all the time when device polling was on.  It is now idle at 0% with device polling off.

Weird though, device polling didn't have an issue running in 2.1.x…

Was affected by the bad SSL certificate problem described in the sticky section.
Had to first use a différent IP on the console and then revert it back to the original one through the web GUI.

Issues my certificate through the Windows CA of the company.
Are there special requirements for the SSL certificate?