What log did you see that implies the password had changed? I would guess a more likely explanation is that there were some login failures caused by the new login limitation?

@Vinibo1 Why not state the requirements, instead of posting the Cisco config? I see you have NAT and VLANs and some addresses. Also, what about IPv6? A lot of ISPs are providing that these days.

@antrock85 The FW2B got two physical interfaces. Installing pfSense, one will be assigned as the WAN and the other as the LAN interfaces. That's all the pyhsical interfaces assigned. Now you can create a VLAN (Interfaces > Assignments) to have 'more' interfaces, which will show up as OPT, OPT1 and so on. But to use it/them you have to know how to work with VLANs.

I can't open that. What are trying to do at that point though? SCP to a pfSense-Plus instance in AWS?

@stephenw10 Nice! Thank you Steve!

Ah, nice. Interesting that Unbound is not able to resolve at that point then.

Resolution Thank You First run pkg-static install -f -y pkg Second run pkg-static upgrade -f pfSense-repoc

@stephenw10 thank you. I tried but still the issue. I think there are more URL with netflix on mobile device to whitelist Also I have tested to connect to my company VPN. It works but once connected I don't have access to Gmail whereas if I disable squid it works. Maybe I have to whitelist the network adress of my company which provide internet services ?

Mmm, typo'd pppoe credentials would be an issue I could imagine. Not sure what we can do about that. For the Net Installer at least.

@stephenw10 whenever there is new patches in the pfSense-pkg-System-Patches a new version of the package is built. wouldn't that reflect some kind of update is needed right? Updated: you just said that haha :)

Yup TAC can do it. Or if you send me your NDI (privately) in chat and I can check it. Steve

@usaiat I would only test the wan side first and see if that helps at all.

The cert hashing issue is a known bug in 2.7.0. It's fixed in 2.7.1 and later: https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

Well I would certainly test with Squid disabled. That traffic may not be leaving the WAN.

@kevdog said in Stack trace when starting pfSense - System wont start: /cf/conf/config.xml -- contents of this file are nothing -- it's an empty file That's scary. [24.03-RELEASE][root@pfSense.bhf.tld]/root: ll /cf/conf/config.xml -rw-r--r-- 1 root wheel 1455699 Jul 3 00:47 /cf/conf/config.xml It is the currently used main pfSense config file. It contains all my settings, without it, pfSense "won't work".

I realize this is an old issue, but I have experienced the same problem. I was able to fix the issue by accessing the WAN interface, press save, then press apply.

Hmm, sounds like it's pulled in some invalid signatures. Or doesn't have pre-processors enabled for the signatures it has. And just did it again from the older BE. Try disabling OpenAppID.

Re: Certain characters are being improperly displayed in Google Chrome yet properly displayed in Microsoft Edge Thanks for your responses and suggestions. The problem was solved by thoroughly removing Chrome and ALL its configuration data. I then reinstall Chrome and all is back to normal.