Depends on the network architecture. If it's a workstation VM on the same host as pfS VM, it (Private) would work. But not for Inet access for anything downstream on the LAN, not even the host. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/create-a-virtual-switch-for-hyper-v-virtual-machines
c70e1185-082b-486a-9d22-68b838f04cc0-image.png

My hn0 interface is down, how do i bring it up?

Hello.
I think this issue is https://redmine.pfsense.org/issues/8987
As workaround, you can apply the steps as indicated on https://redmine.pfsense.org/issues/8987

Go to SERVICES - DNS RESOLVER - GENERAL SETTINGS Go to section HOST OVERRIDES. Clic ADD. Type these values:
host: ews
domain: netgate.com
ip: 127.0.0.1 Clic SAVE. Clic APPLY SETTINGS. Clic top left corner (Pfsense logo) and dashboard loads very fast (no slow for 60 seconds)

I tried this workaround using a Pfsense server without Internet connection.

pfBlockerNG is a package and not part of the base system, so that's up to the package author to decide.

In pfSense, generally speaking links to things on the firewall are not forced to a new window. The main exceptions are links to external resources, such as items in the Help menu.

@AndersKeiser said in Can't reach webgui, error took too long to respond:

So the cause of the issue seems to be the wan and lan being on the same network

A router want to (needs to !) route between different networks.
If you have a network A and A on both side (like 192.168.1.0/24 on both sides) you should replace the router (pfSense) by a switch ;)

Yeah that alternate name is not the same as SAN in the cert.. That is so you don't get rebind or http_referer problems..

IP would not be valid there ever..

If you want to do rfc1918 IP in your cert, you would have to have your own local CA sign the cert. There is no public CA that would sign a cert with rfc1918 IPs in them..

I use san for my rfc1918 address in my web gui.. Where did you get that cert? From a public CA, or did you create the cert with CA you have running on pfsense?

Hi,

Users created in the user manager ?
pfSense needs an admin, or two. Not a boat load of people ^^

The build in pfSense "user manager" isn't user IP aware. But you could have a look at other authentication back-ends, like the FeeRadius package. It has huge possibilities - and filtering user(name) and IP's seems possible to me.
No firewall rules needed, promised. Just the very deep learning curve of FreRadius.

Yes, only when I changed to the SFP+ port. When I was using the rj45 port it showed the LAN as being "UP".

I actually went to System/Certificate Manager/Certificates and exported certificate. After that I imported it to my account. I didn't see option to proceed in the web page for some reason. I hope this will work. I'll update results tomorrow if problem persists.
Thank you for your help Renat.

Youe welcome ☺

@phdemartin

Someone above mentioned setting an IPv6 tunnel. I did that for a few years before my ISP provided IPv6. I could configure for a prefix, as I did on my home network or a single address, which I used on my notebook computer. Perhaps that would work for you. It would also provide IPv6 for your guests.

@jimp

Hmm, ok. Oh well, I guess I'll have to think of a creative way to server the WPAD file. Thanks!

There is no single function. The entire bottom half of the BLOCKED page code is dedicated to reading the alert log, parsing the results and then displaying them on the web page.

What you want to do will require rewriting large parts of the ALERTS tab code as well. The code currently saves no sort of "ID" that uniquely identifies each alert entry in the log, so creating a URL link from the BLOCKED tab to the ALERTS tab is not feasible without also rewriting the ALERTS tab code.

@cerberus128 This is exactly what I have found. I wish I had came across this thread sooner!

I am running the same version and found that if more than 6 interfaces are added, it breaks the graphs as well.

I just wnated to make a topic about this behavior. Strange things i have the drop down menu fixed, and it doesn'work (can't see al the entries) on my laptop, but works great on Tablet (when i scroll on the page the entries starting showing up)...

no problem - was just curious.. Prob not an issue unless major bug issue anyway - and then only if the user is running into it. Sure if was something major an update would be done like pX to whatever the release is for example. Thanks.

You could make a full pfSense package out of it. It's your surefire ticket to fame & fortune!

yes, the problem has been corrected for 2.5.0 development at the moment,
idk if it will be merged for 2.4.4
https://redmine.pfsense.org/issues/9681

@kiokoman Thank you, strange ... since I use several OSes to access it, and several browsers too.

FF / Chrome / Safari
Windows / MacOS ...

All of them. display that issue, and for a long time, but since I had to reinstall the PF I decided to do it 'by hand' and this is very annoying.
Hence the question.
Thanks
Regards.
JG

@johnpoz thanks I see.

@Callan05 I updated the script a little bit, now it's no longer necessary to look up the old certificate and key, the script does that itself :) One thing needs to be checked, the name of the certificate to replace in pfSense, in this script the name contains "WebConfCA". If it's called different, that needs to be replaced.

#!/bin/bash host="ipaddress" username="username" password="password" certificate="certificate.pem" privatekey="privatekey.pem" mv $certificate $certificate.combo csplit -f $certificate.part $certificate.combo '/-----BEGIN CERTIFICATE-----/' '{*}' for file in $certificate.part*; do echo "Processing $file file.."; output=$(openssl x509 -noout -subject -in $file); if [[ $output = *CN*=*.* ]] then mv $file certificate.pem fi if [[ $output = *Authority* ]] then mv $file CA_LetsEncrypt.pem fi done cert=$(base64 $certificate) cert=$(echo $cert | sed "s/ //g") key=$(base64 $privatekey) key=$(echo $key | sed "s/ //g") sshpass -p $password scp $username@$host:/conf/config.xml config.xml oldcertificate=$(grep -A4 -P 'WebConfCA' config.xml | awk '/<crt>/ { print $1}' | sed "s|<crt>||g" | sed "s|</crt>||g") oldprivatekey=$(grep -A4 -P 'WebConfCA' config.xml | awk '/<prv>/ { print $1}' | sed "s|<prv>||g" | sed "s|</prv>||g") if grep "$cert" config.xml > /dev/null then echo "Identical certificate found, renewal not required" else echo "Certificate not found, renewal required" sed -i -e "s|$oldcertificate|$cert|g" config.xml sed -i -e "s|$oldprivatekey|$key|g" config.xml sshpass -p $password scp config.xml $username@$host:/conf/config.xml sshpass -p $password ssh $username@$host rm /tmp/config.cache sshpass -p $password ssh $username@$host /etc/rc.restart_webgui find . -size 0 -name $certificate.part* -print0 |xargs -0 rm -- rm $certificate.combo rm certificate.pem rm privatekey.pem rm CA_LetsEncrypt.pem rm config.xml fi

https://docs.netgate.com/pfsense/en/latest/firewall/remote-firewall-administration.html

@Aililan said in Cannot log in to Web GUI after LAN IP change:

under Ethernet it says "self assigned" IP address 169.254.57.209

That means it couldn't get an address from the DHCP server, so the OS self-assigns an APIPA address.

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

@bulletproof Try 2265.

if (strlen($serial) >= 10 && strlen($serial) <= 16 &&

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.