USG Flex 100 refusing to connect to a Virgin Hub 3 via DCHP and static IP

Xydocq

quote: Your last image shows what I assume is the USG's own internal server however that is not available once the device is configured for Nebula.

That's not true. Every device can be a accessed locally, even it is configured to work with Nebula. On the USG Flex series you can edit the WAN Port and run some tests. That's all you can do there. Every other setting is not available. The way to go, is to run the USG at first in DHCP mode for WAN access then log on to it locally and set the Static connection. I guess my Screenshots are proof you can access the USG Flex locally while managing is done thru Nebula.

Also:

For switches and APs, if you enable Administrative Access on Nebula, local access is disabled. If you do not enable it, you can access them locally. You can't change any settings locally but that's another story.

Btw: If you want to run the Internet Box in Router/Modem Mode. All you need to do on the USG Flex is to change the WAN connection to DHCP. And it will be online. The Internet Box should be available thru 192.168.100.1, so the subnet 192.168.100.0/24 should not be used internally. DHCP and WiFi will be disabled on the Internet Box.

PeterUK

So your back to Nebula and it don't work?

Either VM hub in router mode is blocking connection to Nebula or its VM DNS block the lookup to Nebula.

I would think that if the USG couldn't connect to Nebula that the defaults would work?

The VM hub maybe setup to only allow LAN IP's even if static within its DHCP pool this is possible why? ask the one who coded the hub to be that way.

Also I've seem you say this before "Devices cannot ping 1.1.1.1 as the USG is not connected to the Hub, thus no way to communicate to the outside world" you make it sound like the USG is not connected to the hub at all🤨