[BUG] Obsidian Connector Broken

[mario872]

Bug Description

When connecting the Obsidian connector SurfSense says it can't find any files in the folder, then refuses to let me create a new Obsidian connector, or delete the existing (broken) one.

Deployment Type

• SurfSense Cloud (hosted version)
• Self-hosted version

Steps to Reproduce

1. Build SurfSense desktop app from source and point to a self-hosted SurfSense instance (with volume mounted to Obsidian vault).
2. Open the app and try to connect Obsidian.
3. Fill out all required fields in Obsidian connector settings.
4. Wait a few minutes until SurfSense says it can't find any files in the folder.
5. Try to create a new Obsidian connector.

Expected Behavior

A new Obsidian connector is made or there is a way to delete the broken Obsidian connector or the connector is not broken in the first place.

Actual Behavior

SurfSense pops up a notification in red in the top right saying: "A connector with type OBSIDIAN_CONNECTOR already exists in this search space."

Screenshots/Videos

Environment Information

• Browser: SurfSense Desktop App
• Operating System: MacOS 26.3
• SurfSense Version: 7c61668

Additional Environment Details (for Self-hosted only)

• Deployment Method: Docker/Docker Compose

Additional Context

The self-hosted SurfSense instance is running from the Docker Compose in docker/ with a volume mount from my Obsidian vault to /app/obsidian-vaults/my_vault. Running ls /app/obsidian-vaults/my_vault in the backend container shows my vault contents, yet SurfSense said it couldn't find any files/folders, then didn't let me delete that connector to try again with a new one.

Logs/Error Messages

I couldn't find any error logs in the backend container.

Checklist

• I have searched existing issues to ensure this is not a duplicate
• I have provided all the required information above
• I have added appropriate labels (bug, deployment type)