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.

Thank you!
You're right, firewall access is not ideal in this case. But it's necessary for us to let people manage their port forwarding rules, so this is a preliminary solution we can live with. I hope they change this behaviour in a future release.

@bfred said in [Solved] Lots webgui, page doesn't load:

it didn't break just after saving it (or applying it?)

What you saw was the proof of having a stateful firewall.
Initial connections going trough the firewall rules are matched with the firewall rules, top to bottom.
If one rule matches as a "pass", a firewall state is created, and subsequent traffic bypasses the firewall, because it's known as accepted. This accelerates a lot traffic throughput.
As long as you do not edit the initial matching rule, the state keeps up. Even when you add or edit a rule above your initial rule that would block such a connection.
To really apply new rules that do not "seem to work right away" you have to manually reset the states, or, same thing : reset the firewall as does a reboot.

See Diagnostics > States > States and Reset States.

@bfred said in [Solved] Lots webgui, page doesn't load:

https port from 1 machine to a different port on that same machine

A device on the Internet ?

thanks much for the advice,

i figured out how to setup the openvpn.

the wizard was pretty good.
took me a while to figure out the the wizard does not create a user in the local user database.

i have an account with packtpub.com.
they have several books on pfsense.

i like my sg1100,

Thanks jimp: done as suggested: Feature #10340 (https://redmine.pfsense.org/issues/10340)

You are correct. I looked at the the system.log and it is complaining about another 192.168.1.1 with a different mac. I workaround the problem by using 10.x.x.x instead for LAN

double post, the answer is here
https://forum.netgate.com/topic/151051/i-can-t-access-user-maintenance-on-a-user-other-than-the-admin-only-the-option-to-change-the-password-appears-even-when-in-the-admins-group/2

@pfSenseTest said in Cert Manager:

Already updated.
https://redmine.pfsense.org/issues/9825

Yep, we already saw that last week and enacted the lower lifetime. New installs will have the GUI cert set to that lifetime, or you can make a new one when pfSsh.php playback generateguicert if you're on a release or snapshot with the change.

Just the GUI cert lifetime change is in 2.4.5, but for 2.5.0 there are more benefits.

For example, the GUI has a visible warning when you exceed the limit for a server cert:

Selection_200.jpg

Plus in 2.5.0 where you can renew a cert in the GUI, there is an option to apply the lower limit at that time.

Selection_199.jpg

I disabled the Dashboard auto-update check.

The host that I am using to access the webGUI uses the pfSense as the DNS resolver. Upstream from that the pfSense is on a domain with a DNS role.

It's probably HSTS cached by your browser giving you trouble and not anything in pfSense itself.

You shouldn't be using HTTP anyhow. Keep the GUI on HTTPS.