Broken AIO <-> Whiteboard integration

Configuration:
VM1 with NGINX. My domain served (proxypass to dockerhost for Nextloud)
VM2 (Dockerhost) in LAN with Nextcloud AIO installed

"Whiteboard container" checked in AIO interface

Whiteboard and nextcloud started successfully:

nextcloud-aio-nextcloud             23 hours ago   9000/tcp  Up About an hour (healthy)
nextcloud-aio-whiteboard            23 hours ago   3002/tcp  Up About an hour (healthy)
........ excessive output cut .......

Container log:

[dotenv@17.2.3] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit
Creating Redis client with URL: redis://:.........cut.......@nextcloud-aio-redis/0
WebSocket compression enabled
Setting up Redis Streams adapter
Redis Streams adapter set up successfully
Server initialized with redis storage strategy
Metrics disabled
Listening on port: 3002 (all interfaces)
Server started successfully on port 3002

Check connection:

From inside "nextcloud-aio-nextcloud" container:

nextcloud-aio-nextcloud:/var/www/html# curl http://nextcloud-aio-whiteboard:3002 
Nextcloud Whiteboard Collaboration Server
nextcloud-aio-nextcloud:/var/www/html#

Great success!

From system: ( spoiler - EPIC FAIL)
localhost

root@DockerHost:~# curl http://localhost:3002 
curl: (7) Failed to connect to localhost port 3002 after 0 ms: Connection refused

LAN IP of DockerHost

root@DockerHost:~# curl http://10.200.200.60:3002
curl: (7) Failed to connect to 10.200.200.60 port 3002 after 0 ms: Connection refused`

explict 127.0.0.1

root@DockerHost:~# curl http://127.0.0.1:3002 
curl: (7) Failed to connect to 127.0.0.1 port 3002 after 0 ms: Connection refused

Port 3002 NOT occupied

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:11000           0.0.0.0:*               LISTEN      2272/docker-proxy
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      5718/sshd: root@pts
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2317/docker-proxy
tcp        0      0 0.0.0.0:3478            0.0.0.0:*               LISTEN      2182/docker-proxy
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      934/mariadbd
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      781/systemd-resolve
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      883/sshd: /usr/sbin
tcp6       0      0 ::1:6010                :::*                    LISTEN      5718/sshd: root@pts
tcp6       0      0 :::8080                 :::*                    LISTEN      2326/docker-proxy
tcp6       0      0 :::3478                 :::*                    LISTEN      2202/docker-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      883/sshd: /usr/sbin
tcp6       0      0 :::80                   :::*                    LISTEN      895/apache2
tcp6       0      0 :::443                  :::*                    LISTEN      895/apache2
udp        0      0 0.0.0.0:3478            0.0.0.0:*                           2224/docker-proxy
udp        0      0 127.0.0.53:53           0.0.0.0:*                           781/systemd-resolve
udp6       0      0 :::3478                 :::*                                2231/docker-proxy

Problem:
When started by Nextcloud AIO, nextcloud-aio-whiteboard not listening on host IP and cannot be accessed from VM1 with NGINX
Port 3002 is available only by direct connection to container

Start by reproducing the reported Nextcloud AIO deployment with the whiteboard container enabled, then inspect how port 3002 is exposed between the container, Docker host, and NGINX VM. Done means the whiteboard service is reachable through the configured host or reverse proxy, not only directly from the Nextcloud container.