php-fastcti is dead for some reason, that's the source of the CP issues. The GUI doesn't use that though, something diff happening there. Could be a common cause making them both fail, like a dying drive might lose the ability to read a file (your session) making you log back in again, though usually those types of failures are severe enough that you won't be able to log back in at all as it'll fail to write the session.

@Exolon: Remove (delete) all references to: style="height:25px" Thanks, I just edited the value and got it close to what I wanted…  removing it makes it perfect (for my needs) Rick

The CPU frequency is only printed when it is not running at full speed. So if that third line is omitted, the CPU is running full bore and is not stepped down.

Hi. Please read this first: pfsense portal page PHP Then, when you are able to detail your question, post back here.

The admin password is unrelated to the proxy password. Your browser auto-filled it if it's set there, just clear it and make sure it remains that way if you save further changes on the page.

If the menu text is changing then sshd is starting/stopping. There wouldn't be any script or anything if you didn't add one. Guessing it's not really running and the logs you were seeing are old. Run 'ps ax | sshd' to see whether it's running.

^ when the tools are used correctly and understand how they work they are very helpful.. I love my lastpass for example..  But yes sometimes it can put in the wrong info. Are you using any sort of sync software for site passwords like lastpass or firefox sync?  You can even sync sessions across browsers, which another thing that can cause problems if not clear on how it works, and that your using it, etc.

What are your settings in: System > General > DNS Servers Services > DNS Forwarder Services > DNS Resolver Services > DHCP Server On the tab for your inside hosts, what are the DNS Servers

You can install your CA into any device that does SSL, why do you need a publicly trusted CA for your webgui??

OK i resolved it… the problem was that my pw was written on Ubuntu and i used pav num for numbers... so that worked from my internal ubuntu but not with windows.......  :-\

Yeah, that was my thread (https://forum.pfsense.org/index.php?topic=102069.0). I'm interested to see what comes of this too. Although ssh and logging in to the pfSense box itself are workarounds, using the GUI would still be easier and there is no reason why that shouldn't work as epected. I too had thought it was the size of the file, but there may well be something else going on, or more than one issue. Either way, the "Edit File" and "Filer" functions don't seem to function as well as they might.

@Gertjan: The most simple way to access 'pfSense files' is : use a vanilla FTP-client, like  FileZillaFTP (or much better: SmartFTP) and access your box using …..... SFTP. Use a good text editor like Notepad++ (or much better: UltraEdit). It all becomes a question of "click-open-edit-save". IMHO: GUI-build-in-edit-options are just 'poor-man's solutions'. I'd rather prefer SSH in and use nano. Yeah - I'm perfectly happy SSH-ing in too. In fact real men don't even SSH, but log in to the box directly ;)

good job, very useful, thank you.

"I'm wrote a script under /usr/local/www/XFOLDER for manage freeradius mySQL database" WHY???  When there is already a freeradius package is my question.. Why would your script need APC disabled??  Why not just put your script on where the freeradius is running and your mysql is running - trying to run the script on a firewall that is a custom distribution of the OS and the software running like lighthttpd, php, etc.. Make NO sense to do what your doing..

I don't think it's just me? The "modern" browsers start to behave in completely idiotic ways when it comes to forms/usernames/passwords/logins: offering to save credentials for fields that are not username/password at all trying to autofill saved credentials on completely wrong places unwantedly filling in complete crap on clicking submit various cookies SNAFUs now Mozilla has come with a "wonderful" idea to scream about lack of HTTPS on login forms :( >:( >:(

Pull requests have been committed, so this should be working in new snapshots of 2.2.5-DEVELOPMENT and 2.3-ALPHA