Default webqui location

Questions
1

Your question

Where is the default webqui installed on linux

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

The WebUI is not stored as a static directory on disk in the traditional sense. It is delivered as a downloadable Application bundle that Stalwart fetches automatically from GitHub on first start, then refreshes on a schedule. It is served by the server itself at /admin (management) and /account (per-user portal).

There is no fixed filesystem path like /usr/share/stalwart/webui to navigate to. The server handles the bundle internally. To access the WebUI, point your browser at:

  • http(s)://<your-server>/admin for the management interface
  • http(s)://<your-server>/account for the end-user portal

If /admin returns 404, it usually means the initial bundle download from GitHub failed (e.g. no outbound HTTPS access). In that case, verify the host can reach github.com and objects.githubusercontent.com on TCP/443, or configure an internal mirror via the resourceUrl field on the Application object.

Relevant docs: WebUI Overview and FAQ: Why does /admin return 404?

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

3

FWIW the webUI is WASM. If you want to edit it, you’ll have to dip into the source code and then recompile.

4

Yes, but where does stalwart download it to, so I can veryify its downloading

5

There isn’t a traditional on-disk webroot for it. The admin UI is a bundle Stalwart downloads from the configured resource URL and caches in the blob store (the data store), not the filesystem. At runtime it’s unpacked into a temp directory: the Application’s unpack directory if you’ve set one, otherwise the OS temp dir under a subfolder named by the application id, and served at /admin.

To verify it actually downloaded, watch the startup logs for the resource fetch from the resource URL; if that succeeds, /admin will resolve. A 404 on /admin is the sign the download didn’t complete, usually outbound HTTPS to GitHub being blocked.