Docker image serves 404 for all UI routes

[Bhargav79]

Docker image serves 404 for all UI routes

Environment

• Image: ghcr.io/nullclaw/nullhub:latest (reports vdev)
• Also tested: ghcr.io/nullclaw/nullhub:v2026.3.13
• Deployment: Docker on a remote VPS (no local browser)
• Command run:

  docker run --rm -p 19800:19800 -v nullhub-data:/nullhub-data ghcr.io/nullclaw/nullhub:latest serve --host 0.0.0.0 --port 19800
  

What happens

The server starts successfully and I can confirm it is reachable:

nullhub vdev
listening on http://0.0.0.0:19800
access chain: http://nullhub.local:19800 -> http://nullhub.localhost:19800 -> http://127.0.0.1:19800

However, accessing http://<vps-ip>:19800/ (and variations like /ui, /app) returns a 404. No request is logged to stdout/stderr when the 404 occurs.

What I expected

The README states:

"The resulting binary includes the built web UI; it no longer depends on a runtime ui/build directory."

I expected the embedded Svelte UI (visible in the repo under ui/src/) to be served from the root / path.

Questions

1. Is the UI supposed to be accessible when running in Docker on a headless/remote server, or is it only intended for local machine use?
2. Is the latest / vdev image built with the UI embedded, or does that only apply to tagged release builds?
3. Is there a specific route or additional flag needed to serve the UI when running via serve mode?
4. The README mentions chat functionality — is that available in the Docker image or only when NullHub manages components natively on the host?

Happy to provide any additional debug output if helpful. Thanks!

[DonPrus]

Fixed here - #16