hey@jorbox, I recognized the name 
and it’s not that I wouldn’t share the solution, it’s just I can’t know it, because the real reason is unclear and somewhere hidden on your system.
as said before, I suspect your apache not being able to bind itself to the network interface or port because that interface is not ready at the point apache starts. but it could be other things as well.
I understand that it’s weird to see that behaviour on comparable systems and can’t tell you why that is. maybe you still installed thing in a slightly different order or the network setup differs (do you run a vlan there) - or it’s not related to the network at all and my guess is wrong 
I am sure you’ll figure it out anyway and if you have more info, I am happy to help.