A better forum would be "Traffic Shaping" than "Installation and Upgrades".

Hmm, that is strange indeed.  Well, that one is above my pay grade.  Up to the devs now…

Just upgraded from version 2.1 to 2.3, somehow if I enable proxy, all the traffic will be directed to https, all my users cannot access a lot of the websites, and my users also could access ftp site eventhough I have opened the port on firewall on LAN port, otherwise all works fine.

Good lord the time I've wasted on this. I rebooted the jail and it started responding so I rebooted the server and everything is working now. Sorry for the stupid post, it was PEBCAK.

Your destination would normally be your WAN IP..  Since to be honest that is the ONLY IP it could ever be dest for.

As said on the other thread, I'd like to know if you had the chance to solve.

Hi guy, was wondering if you solved somehow. Cause actually I'm on the same path than you. Thanks in advance.

@Derelict: Get your config how you like it Reinstall fresh Connect laptop to LAN webgui at 192.168.1.1 kill the auto config (click the pfsense logo at the top) Restore the old config (modified for the new hardware) Auto-reboot and you're done. Reconnect to your modems, switches, etc. That is an exact description of my workflow. Several times with 2.2.6 and 2.3. Tried with and without changing the interfaces in the config and it just doesn't work. Tried a fresh install and manually configuring everything and it doesn't work. Tried a fresh install with nothing but a single port forward and it doesn't work. A port forward is so simple and should "just work" but for some reason it doesn't. ETA: Since this seems to be a new/different problem now I'm going to stop replying to this thread and move the discussion to this one.

@alphajoza: So what should I do? try to connect to server via LAN? I use host only adapter for the LAN interface and set its network to something like 192.168.249.0/24. Configure the pfSense LAN with 192.168.249.1 via console option 2 and then the host machine can access pfSense via it's LAN interface.

I have the same issue, I cannot upgrade to 2.3 from 2.2.6 nanobsd 4g 64bit. Same error message as well. "Something went wrong when trying to update the fstab entry" EDIT:I used the built in upgrade and that worked fine.

Diag>NanoBSD, enable permanent rw.

Don't you just love those "interesting" coding issues that collaborate to muck upo your network at will….. Glad you got it sorted out.

I just had a dying power supply cause me all sorts of grief and weird symptoms on another computer.  for my pfsense box,  I think it was a bad cable/connector from my Internet provider.  been rock solid ever since they came out and replaced all the ends and did a signal quality test.

Seems like bad power supply. I replaced it twice, but im going 22 days without a  wan failure so i guess that was it. don't cheap out on power supplies people. At least $60.

In case anyone else ever has the same problem, the issue was caused by virt d not using the hardware acceleration of the cpu in the default ubuntu 16.04 install. Solution was to reinstall with the virtualisation options selected.

Hello sorry to add the issue here but I'm also seeing the following XMLRPC sync errors Failed to transfer file: modifysid-sample.conf @ 2016-05-14 11:54:35 Failed to transfer file: emerging-compromised-ips.txt @ 2016-05-14 11:55:50 as well as the Snort XMLRRPC sync errors Failed to transfer file: emerging-compromised-ips.txt @ 2016-05-14 11:55:50 plus this error (below) which does not make sense since I have made sure to use the same password for the admin user on both systems - checked several times on this. A communications error occurred while attempting XMLRPC sync with username admin thanks

I used the memstick version and let it run for a few minutes and it eventually recognized it; up and running now. Thanks for the help!

Hello Legonerd93, I feel your pain! I had this issue just last week on my new build. I also came across the "trying to mount root from ufs" message. I search the archives and downloaded version 2.2.4 using the 64 memstick serial version and it worked! DQ77KB Intel Pentium G630 Micron 4GB(2x2GB) SO-DIMM 1600 Mhz DDR3 PC3-12800 WD 80GB 7200RPM SATA 3.0Gb/s 3.5” ABS R206-ITX slim case