Edit the source, add it around here: https://github.com/pfsense/pfsense/blob/RELENG_2_2/usr/local/www/guiconfig.inc#L55

@jimp: 2.3 does now have a hit counter on the rules view, though it was reworked a bit in the process. Great! Congrats for all! ;-) []`s Jack

re-installing the PHP might fix this issue.

For security reasons, you cannot access WebGUI via WAN by default.  Spin up a new VM on LAN and use that to access WebGUI.  What's up with the unnecessary poll with nonsense options?

In addition to previous post, I am using a eBox with 1GHz and 1GB RAM at home with pfSense 2.2.6 in nanoBSD mode (a 1GB image on SD card). My 2nd slice still have pfSense 2.2.5 and this behavior happens too (much less times, but still occurs). The pfSense box is not stressed at all. It handles a bare 2Mbit link with two internet boxes adding bandwidth together.

If I want to use Cron to restart apinger once every day. What's the commandline for the restart ? Never Mind google helped me :) https://forum.pfsense.org/index.php?topic=69533.msg442680#msg442680

We print out what the OS reports. IIRC some additional work happened on netstat for field widths though I'm not certain this case is handled better. That just made it into 2.3 yesterday I believe, you might give the beta a try to see if it works there for your case.

@SkyHawk: My problem might be unrelated to yours but I've lost connection to the webGUI too.  It started on the 20th of December.  Only changes made was updating FreeBSD to 2.2.6 .. so yea.. that's probably my cause.  I've had no problems prior to the upgrade and I was able to manage the system with the webGUI.  I'm afraid I have failed to follow my own note to self: don't install any updates until someone else beta test them for a month or so. Same for me on my pfSense slave. WebGUI not running after an update to the latest build. I can restart the webgui but it stops again soon after.

2.2.5 and I tried using Bandwidth and PfBlocker. No dice.

Well that comes down to what public ca you used and their licensing model..  If they don't mind you using a wild card cert on multiple physical machine without more money, or you don't have any moral qualms about it.. Then sure you can run a wildcard cert on 1000's of different machines if wanted too..

Try using the config file override option to specify a your custom DHCP client config file to use.

No need to edit anything, just clear your browser cache.