YAOS server online but Obsidian plugin stays Offline

[Douglock]

Hi! First of all, thank you for YAOS, it looks amazing.

I’m having an issue where my YAOS server appears to be online, but the Obsidian YAOS plugin always shows Offline.

• On the server status page, I see: “YAOS Server is Online”, and the message “This server has been claimed and is locked.”

• The buttons show “Text Sync”, “Attachments: ON”, and “Snapshots: ON”.

• However, inside Obsidian, under YAOS → Sync status, it says “Sync is configured”, but the status on the right is “Offline”.

• In the details below, the Status line also shows “Offline” all the time.

What I’ve tried so far:

• Restarted Obsidian several times.

• Closed and reopened the vault.

• Waited a few minutes to see if the status would refresh.

• Restart the plugin.

• Confirmed that I’m using the correct Server URL and Sync token from the claim/setup page.

Despite this, the plugin never changes from Offline, even though the server looks online, claimed, and locked.

Could you please help me understand what might be wrong, or what extra configuration / debugging steps I should try to get the plugin to connect properly?

Thanks in advance for your help!

[kavinsood]

Hey! I can confirm that is not an issue for everyone. There are a few things that could cause this,

Check the basics in plugin settings -

• The sync token might be wrong
• A typo in the server URL (no trailing slash, no extra path)

If that doesn't help,

1. Check the WebSocket connection in dev tools

Open the Obsidian dev console (Ctrl+Shift+I on Windows/Linux, Cmd+Option+I on Mac), go to the Network tab, and filter by WS. Then restart the plugin (or toggle sync off/on). You should see the WebSocket connection attempt — look at whether it connects at all, and if it closes, what the error code is.

2. Enable debug logging

In Obsidian, go to Settings → YAOS → Debug logging and toggle it on. Restart the plugin, then check the Console tab in dev tools — filter by [yaos]. You'll see the full connection lifecycle, which will tell us exactly where it's failing (e.g. Fatal auth error: unauthorized, Provider sync timed out, etc.).

If you can share what you see from both of those, I can point you at the fix.

Edit: some clarification,

even though the server looks online, claimed, and locked.

The fact that the server is locked is correct. You can access the server's credentials only once. This is done, so that users cannot gain access to your sync chain, if they find your server's link.

If your token is copied wrongly, you will need to redeploy.