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)
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.
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.
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.