Account
- Name
- Account id
- Created
- Devices
- Used
- Quota
obsync
This dashboard is signed out. There are two ways in, both starting somewhere else:
/login?token=<the token> on this host. This
is the recovery path for a deployment with no working device, which is why the token is a
standing credential and not a spent one.
Either way, open this dashboard at an address your browser treats as secure. An
https address works everywhere. Plain http to
localhost or 127.0.0.1 works in Chrome and Firefox but not in
Safari, which sends no Secure cookie to a plaintext origin. Plain
http to any other address or name works nowhere: the session cookies are
Secure and host-bound, and a browser simply discards them.
The dashboard holds no vault key. It can never read a file, approve a device, or recover a vault; those all happen on a paired device.
That token is the recovery sign-in. It stands for the life of the server, it is not spent
by being used, and anyone who can read v1/setup-token on the journal volume
holds it. Prefer Open dashboard on a paired device for everyday sign-in, and
rotate the token if you believe it has been seen: stop the server, delete that file, start
it again.
24 h ago now
Every paired device syncs its selected folders under its own ceilings. Revoking one drops its wrapped secret: its next request fails and no other device is affected.
| Device | App | First paired | Last sign-in | Last seen | Last edit | Address | Country | Per file | Budget | Actions |
|---|
No device is paired yet. The Pairing page has the steps.
Pairing codes are minted on a device, never here. The dashboard holds no vault key, so it cannot approve a device: approval always happens in Obsidian on a device that already syncs.
Devices need this URL. It is whatever the operator set as the server's public address.
not configured
Edge mode is . Every request to
/v1/* must carry the edge's connecting-address and request-id headers, and the
edge's access policy in front of the API is a service-token policy. Issue a service token
there and configure it on the device before pairing, or the server refuses the request with
421 edge_required and pairing never starts.
Writes are refused with 507 below the watermark. Nothing is
overwritten and nothing is lost; the device retries.
A chunk whose stored bytes stopped matching its storage id. It is moved aside, never served, and replaced the moment a device re-uploads it.
| Storage id | Quarantined | Size | Reason |
|---|
No chunk has ever failed a scrub.
Install Obsync inside Obsidian on each computer, phone, or tablet.
If Obsync is not in Browse, its directory listing is not yet available. Installation does not require copying plugin folders manually.
In Settings → Community plugins, select Check for updates and update Obsync. Your vault and pairing stay in place. Each device manages its own plugin updates.
Server plugin .
Your server needs an HTTPS certificate your device trusts. If your server uses private connectivity, connect to that network before pairing or syncing. Certificate errors must be fixed by the server operator.
One line per decision, newest first. Paths are classes, never vault paths, and no line carries key material: the server has none to log.
No decision matches that device id.
used of · free
No history within the retention window.