A very thoughtful reply, and I’ll bet you’re probably correct. The thing that gave me pause, though, was that explosions on cargo ships usually occur because of explosive cargo. The engines use bunker fuel, a heavy oil which is almost tar-like. It doesn’t vaporize at ambient temperatures. The engine room fires that I have heard of don’t tend to cause a ship to sink. I’m no expert, though, and I suppose there are other things aboard that could cause explosions, like batteries for emergency power?

A scooter exploded in Moscow last week, and now a cargo ship carrying military equipment exploded this week? Huh.

I feel like there’s a lot of information missing here. VLANs operate at OSI layer 2, and Immich connects to its ML server via IP in layer 3. It could talk to a remote server in Ecuador over the Internet, so the layer 2 configuration is irrelevant.

What you have is an issue of routing IP packets between subnets. You just need to set up a rule on your router to allow the Immich server on the Internet-facing IP subnet to connect to the correct port(s) for the ML server on the private subnet. Or maybe use the router’s port-forwarding feature. Lacking further information about the setup, I have to be vague here. In any case, it’s conceptually the same as punching a hole in the firewall to let IP packets from an Immich server in Ecuador get to the ML server on your private subnet, except that the server is not in Ecuador.