@stephenw10 said in After 2.5.0 update, Dashboard never receives update statue for version: https://redmine.pfsense.org/issues/11443 The bug report title is: Disabling 'State Table Size' prevents other data being displayed So don't do that. ...or use the patch linked there is you really don't want the state table size displayed before p2. Steve

It's a known issue but there is no real workaround. Resetting the logs also resets the dmesg.boot log which is what gets parsed to check CPU flags for things like AES-NI among others. See also: https://redmine.pfsense.org/issues/11428

@johnpoz I tried accessing web UI from the LAN device to IP 192.168.1.1 I also had tried from a device on the WAN accessing the router assigned IP of 192.168.1.30. Neither worked.

@dennis_s ty i will read up. update: patch applied and working thanks again

@jimp ok, will do in a few minutes Edit: Created - https://redmine.pfsense.org/issues/11510

@jimp said in Command Prompt output in WebGUI 2.5.0: "top" requires an interactive console to output data on a continual basis. It can't work through the GUI. Since there is no active terminal, it only returns the header info. Thanks - on 2.4.5. I could at least see the "frozen" process tree. Its only cosmetic - if I have a real problem I go to the ssh console. Thanks again for your time (in these days) and regards, fireodo

@bobbenheim Excellent, thanks. I didn't know about the bug tracker!

@gertjan Thanks, this does make sense. So essentially the key is to treat WebGUI session like any other regular traffic and configure as needed using firewall rules. Thanks for pointing me in the right direction.

@viktor_g I have a double-NAT setup, pfSense is the exposed host of another router. I have set up this first router to get a new IP-address every night and a cron job in pfSense to reboot pfSense after that. pfSense is running as a gen1-VM in Hyper-V with a passed through intel-NIC (I350 Series) for WAN and LAN and is the router for my whole network at home.

Those instructions are not even for pfSense. You have broken your installation to the point where the best action to resolve it is to reinstall and restore your configuration.

@lachlanw So I assume, the router does NAT between the pfSense LAN and the computers subnet. Does it also natting / masquerading outbound traffic towards pfSense? Are you able to access the internet from the computer?

@gertjan Thank you so much for your kind information. Much appreciated. Good information you have shared. True, through VPN it is the best way & secure way to access. Once again thank you so much. Lokesh Kamath

@topperharly I´ve found the issue during an deep dive into the config.xml The SSL Certs are declared in the CertManager/ and ACME List, but aren´t stored and aren´t part of the Config Backup. So, after recreating the missing three via ACME , i was able to select them in the GUI. Strange Behavior... but now fixed. sometimes it´s worth to look under the hood ;)

@crock2348 I just came up against this. You can still apply the changes at https://redmine.pfsense.org/projects/pfsense/repository/revisions/e2e4c0d5452f36a3e468e43a78f2cc5316e34174/diff manually to 2.4.5-p1 which should pass the scanner