@Stepinsky it works for me? Maybe they were regenerating the docs or something.

@stephenw10

i am running proxmox on PowerEdge T620 2 X CPU 256 GB RAM
CPU Type QEMU Virtual CPU version 2.5+
16 CPUs : 4 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (inactive)
QAT Crypto: No
RAM: 8GB
HD: 10GB

on 2.7.2 never had this issue but only apears after upgrading.
it's only apearing after reboot otherwise no conflect or issue on any functions

@stephenw10 same output here. it show my correct ip8303b1e7-bae0-4d44-a1e4-715311b3f78a-image.png
i've tried the webpage also return the correct ip
43cd85b9-6cf4-4e73-9def-531038010f4b-image.png
@fireodo i've added both of sites, same result
b8262768-6ba7-4612-8138-af1738c7c214-image.png

@stephenw10 that seems like a good guess at this point, reinstall and restore to prior config worked, CE 2.8 is running fine. Thanks everyone!

Mmm, I would try setting the serial console as primary and making sure that works as expected in 2.7.2 when you access it via the BMC.

You could be seeing some issue with an updated driver in 2.8 that affects the video console.

Yes,

I have serial port. Next time I will check report during boot without monitor attached.
I am interested to what's going on.

You can set a static DHCP lease but not set static ARP. Normally pfSense would just ARP for the IP and update the MAC in the table but if you mark it static things like this can happen. 😉

Yup, that is coming in the next installer version though it requires code in pfSense too so it will probably be Plus only at that point.

@jdeloach said in pfSense 2.8.0 full iso/img:

I was never able to upgrade to 2.7.x because of issues with FreeBSD that the BSD folks (all flavors) didn't want to continue to fix.

What issue was that?

Found the solution to disable wireless card from pfsense before installation.
https://forum.netgate.com/post/1214869

@stephenw10 said in Update to 2.8.0 always still starts 2.7.2:

Do you have an upgrade or boot log from the failing boot?

Unfortunately not. I took a different approach yesterday evening: Installed a fresh 2.7.2. (due to the lack of a 2.8.0 ISO), upgraded this without issues and then restored the saved config. Worked without issues.

Thanks for coming back to me.

@patient0
I disabled WiFi in the BIOS and am now successfully running 2.8.0.