Yes, you can't flash the installer on CF card. You need to boot the installer from USB and then can install it to it. However, I wouldn't not install it to CF as it might kill it over time. Instead, I would look for cheap 8-16GB mSATA SSD's. They're pretty affordable these days, from $10 to $20.

@PiBa: Do you have rules with a gateways/shapers/limiters configured? Or floating rules? Or squid is trying to proxy the traffic? Or perhaps you got blocked in diagnostics\tables\webconfigurator-lockout? Or.. um something else :P If webgui works over the vpn then at least the nginx and php-fpm are working it seems.. Thank you for your answer. i had no float rules, after adding a rule in got the access back. big thank you for pointing me to the float rules. I noticed when we use the wangroup as gateway on the firewall rules as a gateway the internet goes down. it works only with any to any and default gateway.

I'm wondering.. should you perhaps be using the 'vga' image instead of the 'serial' one? Assuming the monitor is directly attached to the pfSense box..

For anyone who has this, I was able to recovery fairly easily, I created a USB Stick, and ran all the defaults during install. It kept the previous configuration, and was able to cut back over to it, without any problem. I followed these instructions: 1. (make sure to set your model) https://www.netgate.com/docs/sg-4860-1u/reinstall-pfsense.html# and 2. https://www.netgate.com/docs/reference/create-flash-media.html

i have just upgraded to 2.4.1 i dont use ppoe. i did notice the CPU was going mad and i even gave it another 2 CPU. (VMWare) Thanks Mat

I was able to use my pfSense box between my USG and cable modem without any issues. The only thing I had to do was create a rule within the Unifi Controller as shown in the attached pic. The workflow is Cable Modem -> pfSense WAN (DHCP) ->pfSense LAN (Static 10.35.2.20)->USG WAN (Static 10.35.2.21)->USG LAN (Static 192.168.1.20)->UniFi Switch 24 (Static 192.168.1.21). With this configuration I'm able to log in to the PfSense box and manage it from the Local LAN. Since I have a Windows Domain running I had to make some adjustments due to the fact that the clients need to point their DNS to a Domain Controller's DNS and DHCP. Both Wired and Wireless clients on the LAN can access both the internal network and the internet. With the Guest Wireless networks I set block LAN to WLAN Multicast and Broadcast Data then manually enter the MAC addresses for the DHCP/DNS server and the Controller. This prevents the Guest network from seeing the machines and shares on the LAN while still allowing them access to DNS and DHCP. I understand the USG and Edge are different but the end result should be the same. [image: 2017-10-26_8-47-21.png] [image: 2017-10-26_8-47-21.png_thumb]

Thank you all for your help. I booted the system from a 2.41 disc, accessed the control panel and then updated in the usual way from 2.4 to 2.41. It now appears to be functioning ok

same problems here 3 VLAN Wans 1 of them static ipv4 was connected 2 of them could not connect per pppoe Upgrade to latest Snapshot has fixed, without renaming anything.

Stay on 2.4  Wait for 2.4.2 Long experience…  The problem will appear to enough people and be solved in a soon future update.

@fohdeesha: …Tested on a nexus 6P and an LG something or other... @marjohn56: Is he still posting messages here? Probably not on none iPhone-threads.  ;)

Edit: my pfsense gives up retrying after a while, but it always come back.

Hi, I installed this traffic totals script (or plugin?) and now on the latest PFsense it doesnt work & I get an error: Error: {"vnstatversion":"1.15","jsonversion":"1","interfaces":[Error: Database load failed even when using backup (No such file or directory). Aborting. How do I uninstall this? Thanks, Rich

It always helps to read the release notes. But, release notes are for things that the software cannot handle or very specific unavoidable situations. In this case, running under VMWARE is extremely common and instead of assuming the user will catch the issue, why not simply make the installer add the needed change to the boot loader?? The fact that a patch to correct this, was made, says that it should have been caught in the previous release… It is still great work and it is appreciated, but like I said before, if it is meant to be Enterprise, Production ready, these 'silly' things will drive customers away as well as: "I have never, ever had any upgrade issues with Untangle". @Grimson: https://doc.pfsense.org/index.php/2.4_New_Features_and_Changes#Known_Issues reading helps.

Thanks. The reinstall did the trick.

Yep. I did a backup first. If you have done this right, and you are upgrading to the version 2.4.1 and gets out problems and issues too, I would suggest to do a fresh and full install once more again and also play back the backup file once more again! Just needed a pointer in the right direction which I got on fb from a kind soul. Please ensure that you are using the ADI-AMD-64Bit-Serial version of pfSense! All recovered now, thanks. Keep thre eMMC storage up to date and install a small mSATA that fits your needs and you get a fast backup system! Sometimes time will be not even there, and so you might be able to get a working platform fast back.

pfSense archive (all versions)

@Gertjan: @gklimeck: …... I made Rules in my firewall to match my LAN rules but it can't get out to WAN from a wireless device. What am I missing? Dono. Didn't saw your firewall rules. What about a "pass-all" rule to test? Afterward, you make more specific rules- and test after each new rule - and step back when things won't work anymore. Not a bad idea and I'll get better at this. Thanks, G