I added eth2 as a host-only interface in virtualbox and got around the "vanishing web GUI" bug. When it disappeared before, it couldn't even be accessed on localhost. It was quite literally not listening on 443. This time it stayed up and was accessible on both eth2 and lo.
When I first set up the bridge, br1 gets an IP via DHCP, but has no connectivity otherwise. Can't even ping the gateway that assigned its IP. After a reboot, br1 no longer gets an IP.
Also, my interfaces are fully functional. If eth0 is set to DHCP instead of bridged, it has internet access. If eth1 is set to static, it can communicate with the other VM on the virtual segment and also provide internet access to it. And I did try setting eth0 to NAT instead of bridged in virtualbox, didn't make any difference. The NIC works both ways on DHCP, but I can't get anything through either interface when bridged.
Any help would be greatly appreciated...