Thanks. I ended up taking your advice and setting up another light linux VM to use as simply a browser client.

@Gertjan said in SEC_ERROR_INADEQUATE_KEY_USAGE when accessing the webGUI from Firefox: Hi, Click on [image: 1589532101352-843d4fdc-7408-4ee2-9cf1-fa255668c248-image.png] and you see what cert is used by pfSense, what SAN, if the dates are ok, etc. The Time is set good .. no problem with it This : @jimp said in SEC_ERROR_INADEQUATE_KEY_USAGE when accessing the webGUI from Firefox: You can make a fresh GUI cert from the console with current best defaults with pfSsh.php playback generateguicert This the point .. How i can generate a new cert and from where Please can you help me will generate a new cert. Firefox won't trust it at first, but you can overreirde this. because you know that "https://192.168.1" or "https://my-pfsense.my-network.tld" IS your pfSese and not some hacked site. You can also use the console access to reset GUI access, so that http://192.168.1.1 is useable, so you can inspect with the GUI what the issue is. I did this when i could not access since first time .. and it works with http

@jimp Ok clear. I will monitor what is specifically happens from that IP and dig a little deeper. Thanks for the swift reply.

@KhaledSN Have you tried these methods? https://docs.netgate.com/pfsense/en/latest/book/config/what-to-do-when-locked-out-of-the-webgui.html#add-a-rule-with-easyrule and check that nginx is running and listen on 443: # sockstat | grep 443

@Gertjan Yeah, I restored config via console a couple of times and it didn't help. Something about the GUI got clobbered in the initial update. A reinstall did the trick.

If you want to access the LAN side of pfSense that's running in the vm from within windows. You'll have to create a bridge interface in your host OS then set your pfSense's LAN interface to be bridged to that bridge interface. for example windows | bridge interface | virtualbox | pfsense LAN interface (using the bridge interface in the host OS) | pfsense WAN interface (using the NAT interface in virtualbox) | Internet

Thanks :)

Curious, I looked at one of our routers. Out of 22 IP aliases, mix of host and network, 15 show in diagnostics/tables. When creating a rule though, if you pick "single host or alias" then you can type in the Source Address field to the right and it should dynamically show you matching aliases. Even ones not on the diagnostics page show there for me. They don't show in a dropdown.

@Gertjan, obrigado! Fiz a restauração através do console, opção 15, agora consigo acessar as configurações através do Webconfig. Teve um detalhe, eu tive que efetuar o restar do webconfigurator, depois disso foi possivel logar no Webgui. Mais uma vez, obrigado!

Found it. config.xml remove the member with the ID of 0 (since that is the ID of the admin user). After a reboot it's working.

@Gertjan Thank you, it is working perfectly now after setting it up as you have suggested. Thanks again

Not zombies!!!! Well I did restore this config from awhile ago but I didn't even think I had it active on the last build. Regardless, I went ahead and removed it unless I come up with a reason to use it and then I reinstall it and hopefully that will fix anything broken by an initial misconfiguration. So far it's loading in about 5-8 seconds. I'll continue to check on it while troubleshooting other issues. Thanks.

@jimp I tried what you suggested, but unfortunately nothing changed. Webgui is not available from other subnets.

I changed the "Session timeout" in the System/UserManager menu to 43200 (about one month), and so far there haven't been any more forced logouts. Perhaps there is a problem with setting this value to "0"? Let's wait and see.