@kiokoman Yes you did! I was blinded by it I guess!

@bulletproof Try 2265.

Maybe rename the box to fw_9X0RDX1?
Ignore at will! ;)

I only had three Chrome extensions, none important, so I removed them all. Still timed out trying to connect to pfSense. Then I started Chrome with extensions disabled. Still timed out.

Then my bank started saying "Sorry, our system is currently unavailable. Please try again." after some time when I try to log in. Just like pfSense, my bank has no problem with Firefox, Edge, and IE, which lets pfSense off the hook.

I've killed enough time on this. I'll give Firefox and Edge a try.

Also : the wizard isn't needed.

During initial setup, fill in System => general setup. At least LAN and WAN interfaces, and you're up.

Thank you so much for your assistance. I found out I accidentally change the TCP port on the Netgate when I was setting up The Helm server. All is well now.

Hi Jim,
Applying this patch fixed the issue: https://github.com/pfsense/pfsense/commit/b9ed452dbba4689e6280efa7f503e30809a3d8e4.patch
Thanks.

Looking into issues is never wasted time.. Something really odd for sure going on - have never seen such an issue before.. Which are always the fun ones!

Would be better to try and figure out what exactly is wrong with the install that could be causing such an issue - there are no errors in the log at all? Was this a clean install, or an update? Was it restored from a backup xml from a different or older system, etc.?

Let us know when you have your primary working again.

ACB has been having some issues over the past 2-3 days or so.

@KOM said in Local user in admin group does not have all admin functionality:

cf529cbe33ae53f3f95b37a227da141b97465f20

Thank you, that took care of it.

Michael

The file path that @chadc01e provided no longer exists on the current version, so I thought I'd update the topic for anyone interested in making this change.

As of version 2.4.4 p3, the bar graphs for the System Information widget on the dashboard (memory usage, temperature, disk & swap usage, etc.) are red regardless of the value.

Go to System > General Setup and in the webConfigurator section it will show your theme, our system uses pfSense.

Go to Diagnostics > Edit File and in the /usr/local/www/css/ folder open your theme (pfSense.css). Use the browser search feature (Ctrl +F) for ".progress-bar" and edit this section:

I changed the color from #B71C1C (red) to #4CAF50 (green) that matches the Thermal Sensors, Interfaces, and other dashboard widgets. When finished, click "Save" and reload your dashboard.

sys-info.JPG

I'm not aware of any current feature request for that. If you want to open one, for a future release, feel free to create a feature request at https://redmine.pfsense.org

Could you fix it from the Chrome side by going into the settings menu and playing with the autofill options?

Good luck to you. I've seen several cases of users whose gateway monitoring wasn't working, just as yours isn't, but I don't think the actual cause was ever discovered, or if it was I certainly didn't hear about it.

Thanks All,

Genuinely don't know why i didn't just try the url (facepalm) haha

@johnpoz actually I just saved that to download and read on the planes tomorrow.

Thanks again,

Will G

Valid use cases for sure.. And I also like your suggestion of showing what interfaces rule is bound too, etc.