See issue https://redmine.pfsense.org/issues/7083 for discussion. Looks like this is all being sorted right now.

yes this is obvious if you do to status traffic graph, have not dug into it though just no its way off

there is probably an error about it in logs

which services? whats the error?

@crisdavid:

Did the trick! although I had to do it on a couple of my devices

Yep- if a change happens in the code sometimes the browser needs to be told to forget the old code.

I generally use F-5 or ccleaner between snaps myself..

Thank you - that sorted it.

Merged to RELENG_2_3. Thanks!

That is a much, much different and more difficult problem to solve, and has nothing to do with this topic.

Yes, this is not new - unbound has such issues since it exists in pfSense. It also crashes at random times (once or twice a month) so I've set up Service Watchdog to restart it and send me an e-mail when this happens (currently at 2.3.2_1)

Need change web interface only first page interface
Or when any failed same DNS attack this web interface change

They found the problem. There was a box in the telrad modem called ip pass thru that needed to be checked. It doesn't fully solve the problem however. A port scan on my ip shows all ports closed despite me having some open. PfSense is one that can't be accessed from the public internet and it could on the twc modem. They claim nothing is being blocked.

follow up
it was as you noticed 192.168.x.1 issues where it should have been a .0 also had not noticed last night and should have all info was right in syslog under openvpn tab (kinda embarrassing) can't even guess how many times I use that page but first time with openvpn so guess my eye glanced right over it

Neither that file nor pfSsh.php have changed in months, and when it did it was just the license. Something fishy might be going on with your disk. Might want to reboot into single user mode and run "fsck -y /" a few times to make sure it's clean.

@jdillard is the one who has done the work on this so far not sure where he is at in updates hope this gets cleaned up before 2.4 release

As already noted elsewhere, you need to configure things for them start. Ntopng at least requires the package to be enabled and an interface to be selected. LCDproc requires extensive configuration to be of any use.

also failing on dyndns.org - even to check ip

/services_dyndns_edit.php: phpDynDNS (tmace.dyndns.org): PAYLOAD: badauth

widget shows 0.0.0.0

Thanks
Myk

Indeed, when you say "blocking icmp", do you mean just to their own gateway/routers, or are they blocking all ICMP to anywhere?