I am also having this issue following along with the conversion guide. I click the button and wait, finally I just get a blank web ui view. Update: I did an ls on /dev after pressing the button and saw that it created an new sa1 Went ahead and ran the script, updated, and let it reboot. It did take longer than normal to boot but I believe it was doing a filesystem check. Don't know for sure, as I don't have a console cable available. Just did the update to 2.4.1 from the web ui and everything rebooted again just fine.

FWIW, I recently re-loaded a half dozen old Alix boxes (2D3 and 2D13) with 2.3.5 I used the 2g-nano and they all worked fine. You really need a null-modem cable if you use an Alix.

I just found this thread.  I have this same problem! https://forum.pfsense.org/index.php?topic=140014.0 I can't find much about this or how to fix the error.  It's either because it doesn't like a self signed cert, maybe it doesn't like httpS on an alternative port of 10000 or something else. I did notice I had to put the credentials in this format on the last version "admin" for the user instead of "root".  I haven't tried root… Any insight?  Not much is logged other than it failed in the pfblockerng.log file in /var/log/pfblocker/

@mikeisfly: Duo means it's hyperthreaded, if I remember correctly. I also believe it is 64bit. As far as a single port you can use a switch but the switch will have to support vlans. That's assuming the computer supports VLANs.  Not all do.

Early next week is the current target

I feel relieved and embarrassed that the tool was in my hands all this time…that's how the learning process works, I guess! Wasted all that time searching and researching yesterday!

Provider is Altibox (Norway), and they have both TV and phone, but I just have internet from them. They are sending internet through VLAN 102 and TV signals through VLAN 101. I have IP phone from other company. For TV I use the satellite receiver. It gives better picture quality. Thanks for the tip regarding internal NIC.

Thanks w0w, I'll read up on this thread and see where that takes me

Update: I think in my situation my issue was caused by pf blocker.  I ran the 2.4 update via the shell not the GUI.  Update appeared to go thru fine.  Once the firewall rebooted, No internet.  All DNS errors.  Tried fixing the resolver.  No luck.  I tried to remove my installed packages.  The package manager show none installed.  Prior to the update I had pf blocker, Squid, Squidguard and LightSquid installed. I pulled out my old firewall running 2.3.3 plugged it in and was up running fine,  the next morning, No Internet.  I rebooted the firewall, still not working.  DNS issues.  The pf blocker package was installed.  I removed it and everything immediately started working. Not saying pf blocker is a problem, but in my case.  I should have removed it and reinstalled it after upgrading.  Now off to rebuilding the original firewall. Hope this helps someone. Randy

the problem has turned out to bee i cant install to the built in emmc drive.. but i had since bought a msata and it installed to that.

So After some digging, I think i found the answer… It is a routing issue. When on 10.8.x.x (Strong VPN's internal IP), When trying to access my internal LAN, It has 100% packet loss. I think i found the answer. Thanks Tyler Edit: I reconfigured the Outbound Manual NAT and got the routing issue fixed. It still looks like their is a port forwarding issue with OpenVPN on pfsnse 2.4.1

https://forum.pfsense.org/index.php?board=39.0 Look at the article on StrongsWAN at the top of this forum..  Plus more than a few examples in the included threads. ;)

Hi, same problem of post #18 here on J3455M-E mobo; I was doing a fresh install because upgrading from 2.4.0 to 2.4.1 through the web console brought to an increase of load average always over 1. Up to now the only solution was to install 2.3.4 version and wait for a solution on something that seems related to the last kernel.

Pleas euse the ADI image to reinstall and play back then the backup file. That´s it, ready in ~15 minutes!

Like you mentioned, I think it may be a firewall rule issue. I am slowly getting better at understanding the logic to them but still struggle from time to time. VL10 Rules Before posting this reply, I created a rule at the top of VL10: Source: VL10 net Port: * Destination: VL10 address Port: 53(DNS) I have previously been successful using this rule which was created from the tutorial I linked above: Source: VL10 net Port: * Destination: LOCAL_SUBNETS (an alias with all VLAN Subnets) Port: Allowed_OUT_LAN (an alias with DNS in it) General DNS Resolver Options Network Interfaces: VL10 is highlighted Ping $ ping -c 5 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. 64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=0.243 ms 64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=0.206 ms 64 bytes from 192.168.10.1: icmp_seq=3 ttl=64 time=0.222 ms 64 bytes from 192.168.10.1: icmp_seq=4 ttl=64 time=0.189 ms 64 bytes from 192.168.10.1: icmp_seq=5 ttl=64 time=0.211 ms --- 192.168.10.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4049ms rtt min/avg/max/mdev = 0.189/0.214/0.243/0.020 ms netstat -an Proto Recv-Q Send-Q Local Address          Foreign Address        (state) tcp4      0      0 192.168.10.1.53        *.*                    LISTEN DNS Resolver logs I changed the verbosity level to 5, restarted the service and checked the logs setting so it would show 600 logs. I didn't see anything about binding to the IP. I searched for 192.168.10.1 as well. I ordered 2 SuperMicro SATA SSDs and will be re-installing in a few days but would like to understand where I am going wrong. Also, thanks for the help. I'm learning a good amount from this thread. Networking is one of my weaknesses EDIT I found the issue with mine. I had set a NAT rule to forward 5353 to 53 when the DNSResolver "broke" so I could use the DNSForwarder. While troubleshooting, I deleted the firewall rule in the VL10 rules page but forgot to delete the VL10 NAT rule. Deleted the VL10 NAT rule and all is well now. I feel accomplished and like a dumbass at the same time!