@xpxp2002:

…. How do I go about formally reporting this to investigate/get into the bug queue?

Go here pfSense Forum » pfSense English Support » webGUI and read this thread Typo error.

Ideally, a PR on Github is best. Tickets on Redmine are OK as well. Main problem with posting these on the forum is that they're easy to miss.

@wizencrowd:

For a school project I need to configure a server with pfsense. We want to use it as a captive portal. My problem is that I can't get in the WebGUI when I have my Wan connection plugged in.

What ??
(but you explain why afterwards …)

When I freshly booted my server I need to unplug the wan cable, then I can login in pfsense. After that I can plug the wan cable back in an everything works. Do you guys now How i can fix this? When I booted the server I don't have internet, but when I login in pfsense I get internet.

@wizencrowd:

Some info that might be usefull:

Lan IP : 192.168.1.100

Wan IP : 192.168.1.103 (DHCP)

Thanks for the info.
You totally broke one of the most important rules when it comes routing.
KEEP LAN on 192.168.1.1/24
Make WAN something 192.168.2.1/24 or 10.0.0.1/16 but NOT in the 192.168.1.1.1/24 segment.
IF your WAN needs to be in 192.168.1.0/24 then make your LAN (example) 192.168.2.1/24

Remember : your are operating a router/firewall, not a switch.

Ok. Thanks.

Trying to get this to work on 2.4.2 but all I'm getting (using jimp's lines, adapted with my own credentials and addresses) is the php page again: it downloads the download php page. It creates the cookies and csrf files but no backup xml file.

Doesn't matter which user I use (admin or dedicated backup user). Fiddled around with the password (for testing now only using a simple word with no fancy characters). Wget doesn't generate any errors (because from its point of view everything is ok).

Any suggestions?

Thanks! Perfect :)

Much appreciated

https://forum.pfsense.org/index.php?topic=137391.0

After uninstalling Snort the issue has gone away for me.

Huh. Must have missed the release announcement. I'll drop it in and re-test.

Yeah it's just weird that it doesn't happen here, the lines are always there. The closest I get to a problem is that the number labels kind of move up/down a little as it updates, but only slightly. And that only happens on Mac.

Probably something that either FF will notice/fix or will be fixed next time we update the graphing library.

"if you are not careful you could get back a answer that you didn't actually want."

Which is why is best to always use FQDN ;)  Which is also why I am not personally a fan of search suffix even ;)  You should always use fqdn to be sure!

I assume his isn't connected to the web?  If so, port forwarding to the gui would also be insane.

@gustavovilaverde:

[2.3.3-RELEASE][admin@fw.local]/usr/local: netstat -na | grep 4343
The service is not working.

You don't know that  ;) TEST if it runs (another port ?) and check when it start in the logs, and see if and why it fails.

@gustavovilaverde:

The service on port 4343 should be listen.

I agree.
As said above, pfSense isn't on strike. It will start de web server (web GUI), up to you to see why it bails out (see logs - always the logs - problem ? => see the logs  ;D)

Use also

(you will see the used config files - check them out)
sockstat -l | grep 'nginx'
(to see all the ports used by nginx)

Yes it was me… ::)

There is a setting "Formatted/Raw Display" in Status> System> Logs> Firewall> , which I must have accidentally turned on.

You are right, that is a little weird. I just pushed a fix, which will be in 2.4.2 and whatever 2.3.x release happens next.

https://redmine.pfsense.org/issues/8069

Ok, I solved the issue.

When you are using VM's, be sure the network interface on your host computer did not assign the same address that you assigned for the LAN address of your pfSense firewall. I assigned the network range on VMnet5 to 172.16.1.0/24. Using that information, VMWare assigned the first available IP 172.16.1.1 to the host VMnet5 interface. Not knowing this, I assigned the LAN interface of my pfSense to 172.16.1.1.

I changed the static IP of my host VMnet5 interface to 172.16.1.2 and now I can connect to the WebGUI!