Put a ; character whenever you want a line break. It should be described that way under the custom options boxes.

Here is the start of a powershell script to log in, anyone have any suggestions on getting it to actually work?

#Firewall Hostname $fwhost = "https://firewall.org.org" #Firewall Login Name $fwlogin = "admin" #Password $fwpw = "tacos" $curlout = [string](.\curl\curl.exe -k -s -c cookies.txt $fwhost) $curlout -match "(sid:.{106})" $curlcmd = ".\curl\curl.exe -k -s -b cookies.txt -d login=Login&usernamefld=${fwlogin}&passwordfld=${fwpw}&__csrf_magic=$($matches[0]) ${fwhost}/services_wol.php" echo $curlcmd $curlout = [string](.\curl\curl.exe -k -s -i -b cookies.txt -d "login=Login&usernamefld=${fwlogin}&passwordfld=${fwpw}&__csrf_magic=$($matches[0])" ${fwhost}/services_wol.php) echo $curlout

Hello,

I managed to get to the colo recently and tested on the same lan: I was able to remain logged in to both tabs, so it appears to be something with ssh port forwarding.  I will dig into it some more and get back to you.

BTW: I have not done anything about the potential bad webgui ssl certificates…

--jason

@jimp,

Apologies for delay - thought I had notify turned on…

Cache is cleared.

This appears on the dashboard traffic graph widget.  It will also appear on Stauts - Traffic Graph but not initially (i.e., the graph will work fine for a period of time).  This does NOT happen on the dashboard as it has not been functional at all since the upgrade.

Hope that helps.

Using Chrome-Dev FWIW...

Move the GUI to another port.

You can't selectively bind the pfSense GUI to specific IPs (yet).

It depends on what rule is blocking. Click the red 'x' and see what it says. There are options to stop logging of certain default rules under Status > System Logs on the Settings tab.

Or, for example, if it's from the block private networks rule on the WAN, you can add your own block rule without logging set, and then disable the block private networks option on Interfaces > WAN.

No, didn't help.

What helped, was rebooting the pfSense.

Strange solution.

Please don't call 128-bit encryption capable browsers old, that's very far from the truth. I can not even think of a cipher that uses 128-bit keys for the symmectric encryption and is required by SSL/TLS that is now considered unsecure.

Since it's already in 2.2 there isn't any effort going into making it work on 2.1.x any longer.

I've the same issue here: A LDAP server is configured (for VPN auth) but only using local account (admins) on webGUI.
Moreover theses LDAP connections/lookup can breaks webGUI when LDAP server is down/unreachable (eg. down Internet connection): each page takes about 40-50 seconds to display: I'm guessing it's because LDAP queries that have to timeout before PHP script can continue…

Others have already encountered the same timeout problem:

LDAP Timeout

Incorrect LDAP setup causing Gui lockout

Web GUI is super slow (SOLVED)

It does not matter on which interface or IP the web configurator is listening for online update.

pfSense looks for updates on WAN interface and have to be able to connect to pfSense.com. If your WAN can reach the internet the problem is mostly DNS. Have you defined a DNS server in pfSense (System > General Setup) that can resolve pfSense.com?
Another issue could be that your update source path is not set up correctly. Here in 2.1.3 it's: https://updates.pfsense.org/_updaters/ <plattform></plattform>

Lol found it seconds after creating this thread…. i searched the wrong variable ...

the variable i needed was $server['conns'] not $conn.
i forgot how foreach works ....

//
found the files under /etc/inc/....