Ah yes your right, i 'read' 2.3.1 if kulpreet is still on 2.3.0_1 that explains it. @kulpreet , can you confirm that 2.3_1 is the version your running and not 2.3.1 ? Upgrading pfsense and/or deleting old files as mentioned above should fix this issue. If your still having trouble getting it to run let us know :).

I see things are starting to go on track again. :) Thanks for the hard work!

@PiBa: Hi Dennis, Any particular reason why haproxy failed for your ocsp requirements.? If your willing to try again, or can explain me how to reproduce the issue in a few steps please contact me on irc or open another thread for the haproxy issue. Thanks, PiBa-NL Sorry for my late response. I will try it again with haproxy somewhere in the coming weeks and will post the results here.

Gonna bump this one and ask, would it be worth a bounty and would anyone, with knowledge of the task, be interested?!?!  :-\

If you close the window at that point, it does not continue.

@ricle: If nano dies i have to shredder my alix? Or is there a way to use a usb stick? You can keep running whatever the last release is that has NanoBSD. Current plan is to keep maintaining that branch for a while. IIRC when we drop NanoBSD, i386 is also being dropped, so either way the ALIX can't move forward. It's past time to be seeking a replacement for that hardware, it's been EOL for some time now.

Odds are it isn't hanging on that but with whatever is happening next. What is next there depends on your hardware. Could be CPU/Power related, could be clock-related, etc. It's definitely still initializing the hardware though. There should be an option for a verbose boot at the first boot menu that comes up. Activate it and see if anything more useful is printed.

Check the system log before you reboot. From the sound of it, it's rejecting something in the configuration and going back to what it believes is the last valid one. Also check the config history in the GUI (Diag > Backup/Restore, Config History tab) and see what it shows happening. Either the configuration change is not being written, or it's being rolled back.

"No address record" implies you do not have working DNS on the firewall. Also the package version it's attempting to fetch is old. Make sure your firewall can actually resolve and reach the pkg server.

On 2.3.1 it's always permanently rw and you can't turn that off :-)

Thanks for the really suggestions, I tried the reset like in the video it does nothing, I tried another cable but it did not work, eventually I installed screen and used that instead of putty and managed to connect, so I can confirm the device is not 'bricked' So the problem is that while booting it gets stuck at the point: Trying to mount root from ufs:/dev/ufsid/55411d03bf874893 [rw]... WARNING: / was not properly dismounted WARNING: /: TRIM flag on fs but disk does not support TRIM This is a warning not an error and I would expect the boot process to continue but it does not… So I found an old image I had from when I first got the device of netgate pfsense 2.2.2 wrote that to a usb and reinstalled the firmware now it seems to be up and running i just need to reconfigure it and hoe for the best... Thanks for the help GX

dude if it wasn't working then clearly it was setup wrong.. I have been running pfsense on esxi for years..  Multiple versions of esxi and pfsense..  This is really is clickity clickity sort of stuff.. connect wan phy nic to wan vswitch.  Give pfsense vnic on this vswitch. Connect esxi phy nic to lan vswitch, Give pfsense lan vnic on this switch. Connect this to your physical switch Your vmkern could be another connection into yoru physical lan, or could be port group on your lan vswitch and there you go your done..  You can add more networks/vlans whatever.. Here is typical sort of setup [image: pfsenseonesxi-setup.jpg] [image: pfsenseonesxi-setup.jpg_thumb]

Same here : all ok.

OK has something to do with HSTS, on Firefox i also cant access google any longer.? I try to import the certificat from the box but firefox says its already imported, so i have to switch of squid because people have to work tomorrow. :-(

@JorgeOliveira: Upgrading on Fridays or Weekends is generally a bad idea, as developers won't be around when you need them. I'd recommend, if possible, building some test environments and testing upgrade process before performing it on production systems. … Sorry but its the only way i can do it! Nobody accept to be offline on working days. So normaly i wait 1 week before i do the updates because dont want to drive. Its should be clear the most important thing is the base system come back after upgrade, no matter whats package are causes to fail. Test systems wont help because on some alix it works on other not, all runing the same version! So it was like i mention, boss was not happy and the staff too, i have to drive and it takes 1 day to come back because heavy weather and a lot of traffic. :-( Alix was not responding on LAN and i have to mess around with the serial cable. :-( Dont know what to do now with 2.3.1_5, dont like so frequently updates in such a short time.

Mixing up the LAN and WAN? Many simple mistakes can cause that.

The same procedure with 2.3.1_5

No switch at moment tho they are planned (vlan capable) just trying to set up the 3 VLANs at the moment - when done there will be 3 wifi ssids on one Unifi  ap and wired equivalents I'm thinking it must be a firewall problem as it is allowing connection to the gui and I can edit the pfsense settings from the vlan connection via the pc - just can't get to the WAN

@Gertjan: Although : putting the graph widget in the main menu ….. I wouldn't do that ;) And why not, may I ask?  :o