Obsidian on ZimaOS: Vault Paths, Selkies and Simpler Sync

Bottom Line: If Your Goal Is an Obsidian Vault, Do Not Start by Running the Obsidian Desktop UI in a Browser Container

The 2025 setup combined LinuxServer Obsidian, Selkies, a reverse proxy and a mounted vault. That can work, but it introduces four separate failure layers before you even edit a note: browser security, WebSocket/HTTPS, container volume mapping and the Obsidian desktop process. In 2026, ZimaSpace now surfaces OZSync for Obsidian specifically for backup, cloud access and cross-device synchronization, which is a better first path when the real goal is “keep my vault on ZimaOS.”

The OZSync for Obsidian lists OZSync in the ZimaOS plugin ecosystem.

Choose the Architecture Before Fixing the Container

There are three practical models:

Sync a normal local vault: Obsidian runs natively on your Mac/PC; a sync layer keeps the vault on ZimaOS.
Open a vault over a mounted filesystem: the desktop app points at a mounted share, with the usual latency/offline caveats.
Run Obsidian itself in a browser container: LinuxServer/Selkies streams the GUI remotely. This is the most complex option.

If you only chose the browser container because you thought it was required for ZimaOS storage, simplify first.

If You Keep the Container, Verify Host and Container Paths Separately

When a vault “never appears,” inspect the Docker volume mapping rather than the Obsidian UI:

# example
/media/Notes/MyVault  ->  /vaults/MyVault

Obsidian inside the container can only see the right-hand path. ZimaOS Files shows the left-hand path. The ZimaOS app paths explains this boundary, while Docker's Docker bind mounts defines the runtime behavior.

Fix HTTPS Before Debugging Selkies

Browser-streamed desktop containers can depend on secure browser APIs and WebSocket connectivity. If the app originally refused “unsecure access,” reverse proxying to HTTPS was a reasonable fix. But test the proxy endpoint before adding the vault mount. A working shell of the Selkies page does not prove the Obsidian process or its WebSocket path is healthy.

The ZimaOS HTTPS proxying provides the ZimaOS reverse-proxy model.

When Selkies Opens but Obsidian Does Not

Restarting the container and seeing the streaming shell without the application usually means the container is alive but the desktop process failed. Check container logs, image version, persistent config ownership and available memory. Do not delete the vault while troubleshooting the GUI.

docker ps -a
docker logs --tail=200 YOUR_OBSIDIAN_CONTAINER
ls -ld /media/Notes/MyVault

LinuxServer currently publishes Obsidian as a web-accessible container, but their images still rely on correct persistent /config and host-volume permissions. The LinuxServer Obsidian container is the upstream source.

Keep the Vault as Plain Files You Can Recover Without the Container

An Obsidian vault is fundamentally a folder of Markdown files plus .obsidian configuration. Store that folder on normal ZimaOS data storage and back it up independently. If the streaming container breaks, your notes should remain readable with any text editor.

The ZimaOS backup and ZimaOS app requirements cover recovery and sizing.

Import an Existing Vault Without Rebuilding It

Stop Obsidian, copy the complete vault—including hidden .obsidian settings if you want them—into the host directory, confirm ownership, then start the container and open the mapped container path. Avoid copying files while two independent sync engines are writing the vault, because conflict files and deleted notes are harder to untangle than a simple mount problem.

Use Sync Rather Than a Browser Desktop When You Edit From Multiple Devices

For laptops and phones, a sync-oriented design keeps each device's Obsidian experience local and responsive. That also reduces dependence on a remote browser session and makes offline note-taking possible. Use the browser-container approach when centralized GUI access is specifically what you want, not merely because the data lives on a NAS.

FAQ

Why does my mounted Obsidian vault not appear?

The most common container-side cause is a volume-path mismatch. Verify the host path, container path and permissions before changing Obsidian settings.

Does Obsidian need HTTPS on ZimaOS?

Native desktop Obsidian does not need your NAS web UI to serve the editor. A browser-streamed Selkies container may require HTTPS or correct secure WebSocket behavior.

Should I store the vault on SMB?

It can work, but a local vault plus synchronization is generally easier to use offline and less sensitive to network interruptions.

Can I copy an existing Markdown vault directly?

Yes. A vault is a folder of files. Copy the whole directory, including .obsidian if you want plugins and settings, then point the chosen Obsidian instance at that path.

What is the simplest ZimaOS Obsidian setup now?

If the goal is cross-device vault synchronization, start by evaluating the current OZSync integration rather than building a full browser desktop stack.