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

I also have that issue however in my case only the "Help" menu is wrapped (below "System"). This is very inconvenient.

This seems not to be limited to Firefox: I also have a Mac (Snow Leopard), Screen is 1280x800, bit I'm using Safari (5.1.10).

I had this exact case a few months ago and yes, it was a user with a missing slash or something like that in the XML.

@jimp:

you can create a new entry on System > Advanced, Tunables tab to set hw.syscons.bell=0 to kill that one.

Thanks, that worked.

It exists on 2.2 snapshots, use the theme pfsense_ng_fs

I've up'd to 2.1.3 and the problem still persists.

At the moment that is probably the best way. At least until we add an API to allow such things.

That didn't work… sigh. damn. Argh.

Quite right, that was the screenshot of the default pfSense page I got after install. I should have shown the shot after I assigned the addresses correctly. I tried again this morning and after a lot of simple changes discovered that I had to clone the MAC address onto pfSense. Instant success. Now have a massively overpowered router for the price of a few hours of work. Thanks!

@Wepee:

Can someone able tell me as to what cause this "notice" to alert me
every now and then?

Here are some thread you can review -

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

Hi,

See the same (like) behaviour for the (open)VPN (users) graph.
I have seen the first time I logged into the openvpn as a (usercount)
spike, but subsequent logins do not show. (it shows a "0" flatline)

Rudi

Never worked with any of the 1.8.x m0n0wall configurations.