Thank you SO much!  That got it!

Hey mbi,  I was out of the office for a few days so I have not investigated this fully, but I did find one thing that fixed my issue.  I do not know if it will help your situation, but is something to consider. The order of the DNS servers I had listed seemed to create the problem for me (I haven't looked into why yet). The following order of DNS servers DID cause this package update issue.   internal lan dns server   isp dns server 1   isp dns server 2   google dns server The following order immediately resolved the package update issue.   isp dns server 1   isp dns server 2   google dns server   internal lan dns server So for me, just moving my internal lan dns server to the bottom of the list made the error go away.  I tested this back and forth a couple of times to make sure it was the only change I made to resolve my issue.  As I mentioned, I haven't investigated this further to understand why, and the rest of my configuration may be way different from yours.  But it may give you help. Jeff

:) Thanks so much buddy, that worked great!

Thanx I tried to write here https://forum.pfsense.org/index.php?topic=126597.msg721366#msg721366 But received no ansver. I suppose i'd have to go with UFS /Bingo

I had this issue before. My problem was when I wrote 64bit image to CF card and try to boot on 32bit system. There is no output indicating compatibility issue. It just stuck on bios screen. Got mad, thought pfSense was issue or my system was not reading the CF card. Or image never wrote to CF card. Put CF card back on computer and saw files on the CF card. Vs when installing from CD/DVD the 64bit image will prompt error that 32bit system does not support long version. Learned after several trial and error, the error was on my end. Ensure you downloaded the 32bit CF version for 32bit system. Ensure you downloaded the correct version for your system.

The key part there is where is the device connected that cannot reach the plex server. If it's connected to the switch then that's in the same subnet as the plex server so traffic doesn't go through the firewall at all. If it's connected to a different port on the x550e then you need firewall rules to access between the internal ports. If it's connected to the router then you would need port forwards setup in pfSense to reach the server behind it. Steve

@empbilly: Okay. After many attempts and a lot of research I believe I got it.  ;D I executed the following commands in shell prompt: Re-create the pfsense repo; pkg-static update -f (Re)Install pfsense-base; pkg install pfSense-base After that webGui shows the update for me and I execute the last command in shell. pfSense-upgrade -d Now, everything works! Did not help me! Here my result: pkg: No package(s) matching pfSense-kernel-* Updating repositories metadata… Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. ERROR: Unable to compare version of pfSense-repo Locking package pfSense-base... done. Locking package pkg... done. Any idea?

@mscdex: After a reboot, I started seeing PHP warnings for every PHP module it seems in both the console and a "crash report" notification on the web GUI. The warnings look like this: [28-May-2017 16:17:52 America/New_York] PHP Warning:  Module 'bcmath' already loaded in Unknown on line 0 … Likely could have been resolved by running: /etc/rc.php_ini_setup or on console using option '16) restart PHP-FPM'

I also encountered this error installing pfSense-CE-2.3.4-RELEASE-4g-i386-nanobsd-vga to an older computer. I found the workaround documented in FreeBSD Bug 187015 helpful. https://lists.freebsd.org/pipermail/freebsd-bugs/2016-November/070681.html Hit 'escape' at the pfSense boot menu and enter the following commands: set hint.agp.1.disabled=1 boot [haven't gotten this far yet] once booted, add the following line to /boot/loader.conf: hint.agp.1.disabled=1

same happened again when moving from 2.3.3 –> 2.3.4

I suspect the Mac may be getting in the way there. You might try setting up another internal VM and connecting both that and the pfSense LAN to an internal network only. Make sure that works first. Otherwise check for states in the pfSense state table from the client PC IP. Check for blocked traffic in the firewall log. Steve

@Derek: …in the future I'll know to wait a couple of hours to make sure it's running well. And that's the frustrating part.

The crash specifically mentions bwn0, which is "Broadcom BCM43xx IEEE 802.11b/g wireless". Take out that wireless card and see if it works then. and/or try a 2.4 snapshot.

Thank you! Somehow I assumed that getting it to run in a VM means that the changes were saved in the config.xml file. Loading it with vi and saving it made it work for me, even hn0 was already filled in. [image: done.png] [image: done.png_thumb]

Hi, I have no problem running pfsense on ovirt i think you should either create a at least two vNIC on ovirt and attach it to the pfsense vm for WAN and LAN or PCI-passthrough a NIC to it

There is a new(older) recovery image in the portal, which seems to be working…. Hurrah!

Ok good to know. Will keep a lookout for which variant you will keep.

@Gertjan: Hi, Just an idea : setup the logger ( Status System Logs Settings) to an external log server so you can see up until which point all your interfaces are going down - or the unit becomes brain-dead. Be sure that reflashing to the version before doesn't give you the same situation. It seems this is a good idea to troubleshoot the problem.  I just don't know how to setup an external log server.  At the moment I will be setting up my network like this just to simulate it the problem keeps on coming on PC2 as well as the connected wireless device at UNIFI AP. MODEM–---->ASUS RT-N56(192.168.1.1)------>SWITCH1-------->(192.168.1.2)PFSENSE(10.10.10.1)-------->SWITCH2----->PC2                                                                             |                                                                                            |                                                                             |--------->PC1                                                                          |----->UNIFI AP