On the Windows release binary, msgvault serve starts and the HTTP API responds, but the web UI is not served. Requesting the root path returns a JSON routing error instead of the browser application:
{"error":"not_found","message":"No route matches GET /"}
The README states that the release binary serves the complete browser application and that Node, Bun, and a separate asset directory are not needed at runtime, so this looks like the embedded web assets are missing from the Windows build rather than a configuration problem on my side.
Environment
- msgvault version:
commit: e90bcdc
built: 2026-08-09T13:53:26Z
go: go1.26.5
os/arch: windows/amd64
- Install method: install.ps1
Steps to reproduce
- Install via
install.ps1 (or extract the Windows release zip)
msgvault init-db
- Import or sync at least one account
msgvault serve
- Open the API server URL printed by
serve in a browser
Expected
The web UI loads at /.
Actual
GET / returns {"error":"not_found","message":"No route matches GET /"}. The server itself is running — API routes respond normally.
On the Windows release binary,
msgvault servestarts and the HTTP API responds, but the web UI is not served. Requesting the root path returns a JSON routing error instead of the browser application:{"error":"not_found","message":"No route matches GET /"}The README states that the release binary serves the complete browser application and that Node, Bun, and a separate asset directory are not needed at runtime, so this looks like the embedded web assets are missing from the Windows build rather than a configuration problem on my side.
Environment
commit: e90bcdc
built: 2026-08-09T13:53:26Z
go: go1.26.5
os/arch: windows/amd64
Steps to reproduce
install.ps1(or extract the Windows release zip)msgvault init-dbmsgvault serveservein a browserExpected
The web UI loads at
/.Actual
GET /returns{"error":"not_found","message":"No route matches GET /"}. The server itself is running — API routes respond normally.