@arrmo Did you determine this was actually the aliases? I'm having similar problems with 2.4.0, but hard-coding the IP doesn't seem to resolve the issue. Created a new post with more details here: https://forum.pfsense.org/index.php?topic=138457.0

ARM builds are very specific to the hardware. There are no general builds like on x86/64.

https://forum.pfsense.org/index.php?topic=138123.0

It's working for me, stable 2.4. THX!! :)

Sorry, it was SBK; shit behind the keyboard. Problemm solved and sorry for the interference

I finally was able to replicate it, but it looks like we're doing everything correctly. The specifications of link local addresses all have a scope in the configuration file. It looks like unbound is not too happy about the same link local address being on multiple interfaces, but that's why scopes exist… Checking sockstat, unbound is actually bound to the addresses it complains about, even with the different scopes. It appears to be harmless, just log spam. Someone could report it upstream to unbound if they want.

uncheck host resources in snmp config https://forum.pfsense.org/index.php?topic=138039.0

That is the same as the 502 Gateway Error, you have to CTRL-Z to break process, then you can run commands.. https://forum.pfsense.org/index.php?topic=137103.0

Hi Guys Thank you for that fix - I honestly thought I made a brick  :o Best wishes Bastolino

https://forum.pfsense.org/index.php?topic=138054.0

Fresh install worked perfect, thankyou

Probably do as asked, reassign the interfaces to get yourself access to the webgui again. Make note of what interface names come along em0 igb1 ix2 re3 or others? -make sure you have a backup of the config from before upgrade as soon as possible(hopefully you made a backup before starting the upgrade) otherwise copy the /cf/conf/backup files somewhere asap. it might be that one of the interfaces got recognized under a new name.. figure out which is which. Assuming all nics are still recognized but some names are different than before, then take a old/good backup config.xml and restore it through the webgui, it should then also ask to reassign the interfaces. or edit the config manually before restoring it by putting the correct interface-names.. That should hopefully get you running again..

Thanks, nextboot -D cleared up the single user shell auto-loading. The 10/8 snapshot's been giving me hell, so I had to reinstall with the 10/9 snapshot.  Successfully upgraded to 2.4.0-RELEASE after that.

Tnx pkg upgrade -f did solve this.

@jimp: Try using "pkg-static" instead of pkg, but from the sound of it, a reinstall would be safer, faster, and less problematic. pkg-static didn't help either. Complete reinstall succeeded. Thanks anyway!

@superbree: @curtisgrice: Perhaps some pre-update testing for RC software is advised before deployment in production. Also feel free to correct me but, I don't believe pfSense has any type of Auto update for this exact type of reason. Not trying to be rude, just don't shoot your self in the foot. Perhaps knowing that SG1000 comes preloaded with beta and now RC software direct from netgate before replying and not trying to be rude. It may not auto update but it sure tells the user that there is an update available every single time you log into the default page.  I don't really blame a user for clicking that when it came loaded with it. Yes, I was aware of that. pfSense 2.4+ is the only version supported on the ARM cpu. This is all the more reason to do your research before updating anything important (esp. remotely managed). My guess is that you have learned the lesson as have the users you mentioned. Now you won't make the same mistake again.