Thanks. I'm going to remove it. I understand all that. I am just a bit confused as to why the password isn't just left blank. At least it's an easy fix :)

Thanks again.

thank you

Under Interfaces Localhost?

Quite the old thread you have unearthed, but the answer is yes.

I found this on the web, Nitro Key

User authentication on local computers (e.g. Windows, Linux) and networks (e.g. Firefox, OpenSSH,
OpenVPN, IPSec, OpenID).

@cmb:

The redirect listens on port 80 regardless of your HTTPS port. Just disable the redirect under System>Advanced.

That did it! Thank you!

@phil.davis:

Status->System Logs, Settings - Reset Log Files - that will make sure those are in current format to be interpreted correctly by current code.

This seems to have resolved the issue.  Thank you both for your help!

The best solution is this:
@Derelict:

Install a certificate signed by a trusted root or tell your browser to trust the certificate.

Big problem  ;) : it's won't be 'free'.
I bought a domain name, like 'my-domain.tld' (give or take a few $ a year). Then, visit startssl.com to obtain a free valid signed certificate for 'my-domain.tld' and "portal.my-domain.tld" (I did not take the included 'www.my-domaine.tld').
You get all the files needed to install into pfSense.
Switch portal authentication to https - no errors for all browsers. Works for me for years now.

jimp, that worked for me… thanks

Have same issue, but not working even any of the resets mentioned here…  :-[

"Rough design"
If a hostname is available for a connected IP/MAC combination, it will be shown instead of the MAC:

Capture-hostname.PNG
Capture-hostname.PNG_thumb

@doktornotor:

@TDJ211:

I searched the forums and it appears some users have mentioned BandwidthD being a potential culprit (I had the package installed but have never used it). So I attempted to uninstall package from the Web GUI on my phone and BAMM, now im getting a 503 error from my phone!!

I'd remove the evil package first:

https://forum.pfsense.org/index.php?topic=90830.msg502489#msg502489

Thanks, yea I eventually did after I was able to get web GUI access back but it didnt do anything for the System Logs prob.

So how is gui slow when broken dns related to that bug link that is about "read-only to read-write mount very slow on nanobsd"  I would think these are too completely unrelated issues.. If gui is slow because the media its installed on, how does that relate to being slow when dns doesn't work??

Sorry for the necro but I wanted to add this for anyone else who arrives here via Google.

We've ran into the same scenario with a company we deal with trying to do the Trustwave Scans.

The stuff they test for changes every month and it seems like we fail for something different each time.

I tried the above posted line but we still failed.  After looking around, this is what I came up with:

$lighty_config .= "ssl.cipher-list = \"TLSv1.2:!aNULL:!eNULL:!DSS\"\n";

SSLscan now shows protected on everything.  BTW, you can add sslscan to pfSense via 'pkg install sslscan'

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

https://github.com/pfsense/pfsense/blob/master/usr/local/www/fbegin.inc

Mr Jingles also reported this double-widget thing with pfBlockerNG.
I can't make it happen. The widgets section of my config at home has:

<widgets><sequence>system_information-container:col1:show,openvpn-container:col1:show,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:close,interface_statistics-container:col1:close,rss-container:col2:close,log-container:col2:show,gateways-container:col2:show,interfaces-container:col2:show,services_status-container:col2:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,picture-container:col2:close,smart_status-container:col2:none,thermal_sensors-container:col2:close,wake_on_lan-container:col2:none,ntp_status-container:col2:none,dyn_dns_status-container:col2:show,traffic_graphs-container:col2:close,pfblockerng-container:col2:close</sequence> <trafficgraphs><shown>lan opt2</shown> <refreshinterval>9</refreshinterval> <scale_type>up</scale_type></trafficgraphs> <rssfeed>http://blog.pfsense.org</rssfeed> <rssmaxitems>10</rssmaxitems> <rsswidgetheight>300</rsswidgetheight> <rsswidgettextlength>140</rsswidgettextlength> <widget_snort_display_lines>23</widget_snort_display_lines> <gateways_widget><display_type>both_ip</display_type></gateways_widget> <filterlogentries>8</filterlogentries></widgets>

I am guessing that maybe the "sequence" tag is getting duplicate entries in it somehow?

What does your "widgets" section of the config contain?