Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteYou can self-host Obsidian LiveSync by running CouchDB on an always-on VPS, keeping its data on persistent storage, and placing a reverse proxy or tunnel in front of it. Your Obsidian desktop and mobile clients then connect to that CouchDB instance over HTTPS using the community Self-hosted LiveSync plugin.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The safe deployment order is: prepare the VPS and DNS, start CouchDB with persistent storage, verify its authenticated health endpoint, run the project’s provisioning script, configure HTTPS and proxy behavior, then initialize one deliberately chosen source-of-truth vault and add other devices through the existing-synchronization path.
As an Amazon Associate I earn from qualifying purchases.
What you are building
Self-hosted LiveSync is a community Obsidian plugin. Its documented self-hosted architecture uses the CouchDB Replication Protocol: each Obsidian client synchronizes with a CouchDB database, while a reverse proxy or tunnel provides the public HTTPS entry point. CouchDB runs in a container, and a named Docker volume preserves the database outside the container’s writable layer.
Only CouchDB is required as the application service in the project’s Docker stack. A proxy or tunnel becomes necessary when clients connect over the Internet. Desktop devices restricted to the same private network can use an intranet-only arrangement, but mobile access generally needs a publicly trusted HTTPS certificate.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Component | Purpose | What can go wrong if it is omitted |
|---|---|---|
| VPS | Runs continuously and is reachable by your devices. | A sleeping, changing, or private-only host breaks synchronization. |
| Docker Engine and Compose plugin | Runs the CouchDB container and project configuration. | The documented container deployment cannot be started. |
| Persistent Docker volume or host data directory | Stores CouchDB databases across container replacement. | Removing a container can remove the only server copy. |
| DNS name | Gives clients a stable address for HTTPS. | Certificates and client settings become difficult to maintain. |
| Reverse proxy or tunnel | Terminates TLS and forwards requests to CouchDB. | Internet and mobile clients cannot connect safely. |
| CouchDB administrator account | Lets the provisioning tool create and configure the LiveSync database. | Initialization fails or the database is left improperly secured. |
The project documentation lists Caddy, Tailscale, and Cloudflare Tunnel profiles. Its server guide also documents Nginx and Traefik configurations. Choose one front end rather than exposing CouchDB directly to the Internet.
Prerequisites and planning
Prepare an always-on host
Use a VPS that remains powered on and is reachable from every device that will synchronize. Install Docker Engine and the Docker Compose plugin before deploying the stack. Create a working directory for the LiveSync deployment and decide where persistent CouchDB data and configuration will live.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →There is no authoritative VPS CPU, RAM, or storage benchmark in the project documentation. Do not select a size based on an invented minimum. Start with a conservative general-purpose instance, watch memory, CPU, disk usage, and network traffic while your vault changes, and resize if actual use requires it. Leave room for the operating system, Docker, logs, and backups in addition to the database itself.
Choose the address and trust boundary
For public access, register or use a DNS name and point its A record to the VPS. Decide whether the proxy will be Caddy, Nginx, Traefik, or a tunnel profile documented by the project. A private-network design can avoid public Internet exposure for desktop-only use, but it does not remove the need for authentication or backups.
Create credentials before deployment
Generate a long, unique CouchDB administrator username and password. Do not reuse either value for your VPS account, proxy dashboard, Setup URI passphrase, or vault encryption passphrase. Store the administrator credentials in a password manager or another protected location; you will need them for provisioning and recovery.
Deploy CouchDB with persistent storage
1. Create the deployment directory
On the VPS, create a directory for the Compose project and persistent data/configuration directories, or use the directories supplied by the project’s Compose files. The important property is durability: the only copy of a vault must never exist solely inside an ephemeral container layer.
Recommended Free Tools
If you use a named Docker volume, record its name and include it in your backup plan. If you bind-mount a host directory, restrict its permissions and back up that directory consistently. A volume protects data from ordinary container replacement; it is not, by itself, an off-server backup.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
2. Set the CouchDB variables
Configure the project’s Compose environment with:
COUCHDB_USER: the administrator username you created.COUCHDB_PASSWORD: the corresponding strong password.- The LiveSync database name. The documented default is
obsidiannotes; use another name only if you have a deliberate reason and apply it consistently to the stack, provisioning command, and clients.
Keep the environment file private. Do not commit it to a public repository, paste it into support forums, or include it in screenshots.
3. Start the stack
From the directory containing the project’s Compose file, start the services with Docker Compose:
Free tools Windows power users keep installed
One-click scans. No signup required.
docker compose up -dConfirm that the CouchDB container is running before attempting provisioning. If it exits, inspect the container logs, correct the environment or volume configuration, and start it again. Do not proceed while the database service is repeatedly restarting.
4. Verify CouchDB before initialization
Send an authenticated request to CouchDB’s /_up endpoint through the local service address or the configured proxy. The project README identifies this healthy response:
{"status":"ok"}A different status means initialization should wait. Check the username and password, container logs, listening address, firewall, and proxy routing. A successful health response proves that CouchDB is alive; it does not yet prove that the LiveSync database has been created or that mobile HTTPS works.
5. Run the provisioning wrapper
After CouchDB starts, run the repository’s couchdb-init.sh provisioning wrapper. Supply the hostname, administrator username, administrator password, and database name required by the guide. The script configures the database and related CouchDB settings for LiveSync. A successful run reports:
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
CouchDB provisioning completed.If provisioning fails, verify that the script is targeting the same hostname and database name used in Compose, that the credentials are administrator credentials, and that the endpoint is reachable from the shell where you run the script. Fix the server first; do not try to initialize client vaults against a partially configured database.
Configure HTTPS, DNS, and the reverse proxy
Point DNS at the VPS
Create the required A record for the LiveSync hostname and wait for it to resolve to the VPS. The proxy must answer for that hostname, and its certificate must cover the same name that you enter in client settings. If DNS points elsewhere, certificate issuance and connectivity tests will fail even when CouchDB itself is healthy.
Use a trusted certificate for mobile
Mobile clients generally require a publicly trusted HTTPS certificate. Caddy can obtain and renew certificates automatically when its DNS and firewall prerequisites are correct. Nginx and Traefik examples in the server guide require you to configure certificate management and forwarding explicitly. A private or self-signed certificate may be suitable for a controlled desktop network, but it is not the dependable choice for phones and tablets connecting over the public Internet.
Forward CouchDB at the root path
Mount CouchDB at the proxy’s root location rather than adding an extra path prefix. The server guide identifies incorrect path mounting as a cause of 404 errors for database requests. The public URL should therefore end at the host name (and, if your design requires it, the documented root endpoint), not at an unaccounted-for subdirectory.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Apply the Nginx settings that affect reliability
If you use Nginx, three settings are particularly important:
- Disable
proxy_bufferingfor the LiveSync route when fast-fetch progress stalls. Buffering can delay streamed or progressive responses. - Raise
client_max_body_sizewhen larger requests fail with HTTP 413. Set a limit appropriate to your vault and policy rather than copying an arbitrary value. - Use the root location for CouchDB so database URLs are forwarded without an unwanted prefix that produces 404 responses.
The Nginx and Traefik examples also require correct CORS and proxy-header behavior. Follow the project server guide’s complete configuration for your chosen proxy instead of mixing directives from unrelated CouchDB tutorials.
Restrict direct administration access
Expose the proxy, not CouchDB’s administration port, wherever possible. Use the VPS firewall to permit the proxy-to-container path and limit direct access to administrative endpoints. The administrator account is necessary for provisioning, but it should not be reachable from every network on the Internet. Review firewall rules after enabling HTTPS and test from an external network to confirm that only the intended public endpoint responds.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Initialize the first Obsidian device
Back up before touching the vault
Make a separate backup of every vault before installing or upgrading Self-hosted LiveSync. Keep at least one copy outside the VPS. The plugin listing points readers to Differential ZIP Backup as a backup option, but whichever method you use must produce a restorable copy that you can inspect independently of the synchronization server.
Remove competing writers
Disable Obsidian Sync, iCloud, and every other service that writes to the same vault before migration. Self-hosted LiveSync is not compatible with official Obsidian Sync on the same vault. Two synchronization products can create competing changes, duplicate files, or conflicts that are impossible to attribute after the fact.
Generate and protect a Setup URI
The quick-setup guide uses an encrypted Setup URI beginning with:
obsidian://setuplivesync?settings=The URI contains encrypted connection settings, including credentials. Its passphrase decrypts the URI and is different from the vault encryption passphrase. Store the URI, its passphrase, and your vault encryption passphrase separately. Do not transmit both passphrases through the same chat, email, note, or QR-sharing channel.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the source-of-truth device
On the device whose vault should define the initial server state, install and enable Self-hosted LiveSync in the intended vault. Use the plugin’s first-time setup path, enter or generate the Setup URI as directed, test the settings, and confirm server initialization.
First-device initialization can overwrite or reinitialize server state. Use it only when this vault is intentionally the source of truth for a new or rebuilt server. If the server already contains data that must be preserved, stop and establish which copy is authoritative before initializing anything.
Add additional devices
On each desktop or mobile device, install Self-hosted LiveSync in the target vault and choose the existing-synchronization path rather than first-time initialization. Import the encrypted Setup URI, enter its separate passphrase, test the connection, and allow synchronization to complete before making a large batch of edits.
On a new device, keep the local vault empty or otherwise follow the plugin’s documented onboarding choice so you do not merge an unrelated folder into the server unintentionally. Verify that expected folders and notes appear, then create a small test edit and confirm that it reaches another authorized device.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Operational safety after launch
Back up both data and recovery material
Back up the CouchDB data volume or host directory on a schedule, and retain a separate vault export or archive. Test restoring a backup to an isolated location; a file that was never restored is only an assumption of recoverability. Include the Compose files, environment settings stored without exposing secrets, firewall notes, administrator credentials, Setup URI material, and both passphrases in your recovery documentation.
Watch resources instead of guessing capacity
Because the project publishes no authoritative VPS sizing benchmark, monitor actual behavior. Track disk growth, available memory, CPU utilization during bulk changes, container restarts, and proxy error rates. Set alerts before the disk fills. A full disk can prevent CouchDB from accepting writes and can also stop Docker from recording useful logs.
Keep one synchronization authority
Every device that writes to the vault should use the same LiveSync server and compatible plugin configuration. Do not re-enable iCloud, Obsidian Sync, or another folder synchronization tool on the synchronized vault. If you need a second backup or archival copy, make it read-only or use a backup workflow rather than another active writer.
Plan upgrades and maintenance
Back up before changing the plugin, Compose files, CouchDB image, proxy, or operating system. Record the current image and configuration, apply one change at a time, and verify /_up, the database, proxy HTTPS, and a client test edit after each change. Keep the previous configuration available for rollback.
Troubleshooting by symptom
| Symptom | Likely cause | Checks and corrective action |
|---|---|---|
/_up does not return {"status":"ok"} |
CouchDB is stopped, credentials are wrong, or the request reaches the wrong service. | Check docker compose status and logs, verify the administrator credentials, and test the local service before testing the proxy. |
| Provisioning cannot create the database | Wrong hostname, database name, or non-administrator credentials. | Match the script inputs to Compose exactly and rerun only after the authenticated health check succeeds. |
| Mobile cannot connect | No publicly trusted certificate, DNS mismatch, blocked firewall port, or proxy route error. | Resolve the hostname externally, inspect the certificate name and expiry, confirm HTTPS reaches the proxy, and keep CouchDB administration private. |
| Fast-fetch progress stalls behind Nginx | Response buffering delays progress. | Disable proxy_buffering for the LiveSync route as documented by the server guide. |
| Large requests return HTTP 413 | Nginx’s request-size limit is too low. | Increase client_max_body_size to a policy-appropriate value and reload Nginx. |
| Database URLs return 404 through Nginx or Traefik | CouchDB is mounted below an unintended path prefix. | Forward CouchDB at the proxy root and retest the database endpoint. |
| Notes appear to be overwritten or duplicated | More than one synchronization product or an incorrect first-device initialization was used. | Stop all writers, restore or compare the pre-migration backup, select one source of truth, and re-onboard devices through the correct setup path. |
| The container was replaced and data disappeared | Data lived only in the container layer or the persistent volume was not mounted. | Stop writes, inspect the Compose volume mapping, restore the latest external backup, and correct persistence before restarting clients. |
How this compares with other synchronization approaches
A VPS gives you control over where the CouchDB data and backups reside, but you operate the operating system, database container, proxy, certificates, firewall, monitoring, and recovery process. A managed synchronization service shifts server maintenance to its operator, while a different self-hosting design can change the storage and connectivity model.
| Decision axis | Self-hosted LiveSync on a VPS | Managed or alternative self-hosted approach |
|---|---|---|
| Server operator | You maintain the VPS, CouchDB, proxy, upgrades, and recovery. | The provider or another platform operator handles some or all server work. |
| Data and backups | You choose the VPS volume and backup destination and are responsible for testing restores. | Storage location, retention, and export controls depend on the service or backend. |
| Mobile HTTPS | Available when your proxy or tunnel supplies a publicly trusted certificate and reachable DNS. | May be built in, private-network-only, or dependent on a different connectivity design. |
| Conflict handling and customization sync | Uses the LiveSync plugin and CouchDB configuration you operate. | Behavior varies by product and should be verified before migration. |
| Recovery and migration control | You control database backups, vault archives, credentials, and server placement. | Export formats and recovery procedures are controlled by the service or platform. |
| Ongoing cost | VPS, domain or tunnel infrastructure, storage, and backup costs. | Subscription or infrastructure charges vary; do not assume one model is cheaper without comparing retention and administration needs. |
| Operational effort | Higher: updates, certificates, firewall rules, monitoring, and incident response are yours. | Lower when managed, or different rather than lower when using another self-hosted backend. |
The project listing also mentions object-storage backends such as MinIO, S3, and R2, plus WebRTC peer-to-peer options. Those choices alter infrastructure, availability, and recovery assumptions; they are not drop-in replacements for the CouchDB VPS procedure above.
Quick Recap
Final checklist before you rely on the server
- The VPS is always on, patched, and reachable by authorized devices.
- Docker Engine, the Compose plugin, and the project files are installed in a documented directory.
- CouchDB data is on a persistent volume or host directory, with an external backup.
COUCHDB_USER,COUCHDB_PASSWORD, and the chosen database name are consistent everywhere.- An authenticated
/_uprequest returns{"status":"ok"}. - The provisioning wrapper reports “CouchDB provisioning completed.”
- DNS resolves to the VPS and the proxy presents a trusted certificate for the exact hostname.
- CouchDB is forwarded at the proxy root, and Nginx buffering and request-size limits are appropriate if Nginx is used.
- Direct access to CouchDB administration is restricted by firewall and proxy policy.
- Every vault has a tested backup, and competing synchronization writers are disabled.
- The Setup URI, URI passphrase, vault encryption passphrase, and administrator credentials are stored separately.
- Only the intended source-of-truth device used first-time initialization; all other devices use existing synchronization.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
