Fixed.

For those of you just joining, I edited config.xml and replaced the webGUI port from 10443 to port 80. Once I did that, I could access the webGUI normally.

The interfaces in the factory default config are not the physical devices that are in the APU1D4. It will be reporting interface mismatch on the console and asking to assign interfaces. You need to connect to the serial console…

@josephborg07:

When connecting through the console port, I was getting a blank black screen. When I pressed enter I was provided with the command line interface (still through console). From the console I then made the necessary changes which allowed me to provide myself with access to the web interface

I often find the same thing, that the console goes in to a 'screen-saving' mode and doesn't display anything. With pfSense and Linux in general, I typically use the arrow keys to wake a machine up, in the interest of avoiding submitting a command when I don't mean to (just in case, not like I leave half finished commands just lying around!).

setterm -blank 0 ```will disable this in Linux (Ubuntu), but I can't find anything similar with pfSense myself. Best of luck getting used to your new toys, it's well worth it in the long term.

This bug: https://redmine.pfsense.org/issues/3314

Not be a problem any more.

Yes, you could. You don't by default and that's all that matters, pretty much. Good luck convincing those unfortunate guys that need to mess with AD CA to mess with the templates.

You can export CA cert and private key and use them to create your wildcard cert, which you can just import back (along with private key) to CertMgr. Probably you can do all this on pfSense box using built-in OpenSSL.

The problem was search scope base DN. They are different for pfSense query and ldapsearch command, as it can be seen above.
The solution is to remove "cn=users,cn=compat" part from base DN and leave only "dc=company,dc=com".

A LAN Accounting Suite.

Thanks. Applies and works just fine for both 1/ and 2/.

I am seeing slow GUI response up to needing serial logon and Webconfigurator to restart.
Not using LDAP, however.
Does anyone know if there are any tweaks that can be done in the advanced settings or otherwise
to hasten the response time ?
I am running a new SG-4860 box.

Thanks

Oh I am such a doorknob! Thanks for pointing that out, I hadn't noticed the change in the interface.
Have been working on 2.0.1 too long !

thanks again

cheers,

Chris

The RSS widget is right there.  Use it as a template and write your own widget.  Have it load your URL file instead of fetching the feed from pfsense.org.  Done.

no. Can follow this ticket for updates. https://redmine.pfsense.org/issues/4383

It is fixed on 2.2.x; if you are on 2.1.x then either

clear your freaking cache if on Windows install the MS fonts if you are on Linux.

I remake mine every morning…  Just to be sure.

(kidding - no one should be seeing that except you.  It shouldn't matter if that interface is HTTPS or HTTP in my opinion. )

@kejianshi:

I would reduce my pings from every 1 second to every 5 or ten seconds in that case.

Its just as useful for you and less likely to have your packets dropped as a nuisance.

I did same and my apinger started behaving better.

right thx.

Block access to management ports from source WLAN subnet to "This Firewall" destination. (Assuming pfS 2.2.x)