Not sure how exactly he would think the gui would come up from the wan?  How would you of edited the rules to allow for that?  Or do you mean you hit the wan IP from the lan side??

And again did you sniff on the wan to verify traffic.  Pfsense doesn't give 2 shits what its IP address is to listen on..  So either its not listening?  Or your going to the wrong IP?  Or the traffic is not getting there..  Maybe your office IP changed? ;)

I know this is an old post but…it's been bugging me for 6 months so...  Be nice if it displayed the CPU usage all the time regardless.  Then we wouldn't have to ask these silly questions why it comes and goes. And it's not true that it disappears only when at max cpu usage.  I just built a new box on an Intel Atom CPU and it seems to only show when the speed changes. If I put no data through it and powerd -v shows it's sitting at min 500Mhz rather than max 1700Mhz it doesn't show 500 on the dashboard, it disappears while sitting at the low end as well. So what good is a part time indicator?  Part time operation to me means it's broken.

Exact same problem.  SG-4860  Been at it for days with no solution.

Fixed it - editing the file /conf/config.xml is correct However, I had to delete /tmp/config.cache and restart the gui to make it pick up the changes.

http://mentalfloss.com/article/55895/countries-havent-adopted-metric-system "At this time, only three countries—Burma, Liberia, and the US—have not adopted the International System of Units (SI, or metric system) as their official system of weights and measures."

There's a known but elusive bug that sometimes disables the UI entirely, perhaps it's that simple. https://redmine.pfsense.org/issues/6406 Enable SSH on the unit and SSH in and choose "Restart PHP-FPM" and see if your UI comes back.

Happens on the latest 2.3.2 also. In fact, just happened to me. I suspect it's this elusive bug: https://redmine.pfsense.org/issues/6406 I tried restarting the webconfigurator but it did nothing, never tried the other option as the box is not yet live, just rebooted. Apparently it's more likely to happen if you leave the web page up for a period of time. Thankfully it doesn't affect SSH, and it doesn't affect functionality, so it's an annoyance rather than a bona fide forest fire emergency.

Should be simple enough to make the table sortable. I will look into it later this week.

Usually that sort of error happens because the browser is attempting the wrong protocol on the port. For example, you might have used https://x.x.x.x:yyyy when the web server was actually set to HTTP.

You're better off starting a new thread, a lot has changed since this thread (lighttpd switched out for nginx, for one). From a security standpoint, allowing it to run in an iframe is an awful idea, which is why we have protection against it.

Create an account and submit a feature request here: https://redmine.pfsense.org/

@charlie0440: Is it possible to have an email sent using the smtp settings (system > advanced) when pfsense boots? 'booting' is one thing, pfSense should be able to connect to a mail server, which could be some where on the Internet. This means that interfaces should be up and functional. This is what I tried : Insert notify_all_remote(sprintf("pfSense booted.")); just before the ending "?>" in this file : /etc/rc.bootup I received a mail saying "pfSense booted." when I rebooted pfSense..

@johnpoz: I think the .crt is just confusing you - you can open that .crt file in notepad its just the base 64 encoded file.. Thanks for the reply. Not sure how I missed that.

Nifty!

Changing the periodic backup settings is just a cron job change.  So reboot is not required for that to be applied. Changing the size gives the message, "The changes have been applied successfully." even though it has not actually been changed, and there is no instruction that a reboot is needed to complete the change.

AWESOME! That did the job, I have looked at that screen about 100 times and never noticed that option, thanks heaps for that :)

That way was chosen because it fit the current user privilege mechanism. If it was done some other way it would have vastly increased the complexity of the code for very minimal benefit. Selecting everything is never necessary, just pick the "all pages" privilege and a maybe ssh and whatever else someone needs. We have never recommended selecting them all and it's never been necessary. You also never, ever need to edit the group permissions for the admin group, it has all access by default. We don't lock it down because there may be some unforeseen need, but that is also a bad practice. We can only go so far to prevent foot-shooting. As for regaining access, the config can be edited by hand at the console using viconfig, or you could use scp to fetch a backup copy of the config and then edit out the privilege, scp it back and restore it from the console.

Looking at rrd_fetch_json.php, I notice that "step" is taken from the rrd data file itself. So it could be something with the data or at least the data collection process.