# Syncing Error: 'Could not open file, no such file or directory'

**URL:** https://discourse.joplinapp.org/t/syncing-error-could-not-open-file-no-such-file-or-directory/44781
**Category:** Support
**Created:** [8 April 2025 22:30 UTC](https://discourse.joplinapp.org/t/syncing-error-could-not-open-file-no-such-file-or-directory/44781 "2025-04-08T22:30:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![UltraJon](https://avatars.discourse-cdn.com/v4/letter/u/958977/32.png) [@UltraJon](https://discourse.joplinapp.org/u/UltraJon)
#### Post date: [8 April 2025 22:30 UTC](https://discourse.joplinapp.org/t/syncing-error-could-not-open-file-no-such-file-or-directory/44781/1 "2025-04-08T22:30:36Z")

</div>

### Operating system

Linux

### Joplin version

3.2.13

### Sync target

Joplin Server

### What issue do you have?

Hi all, I am wondering if you can help me with this syncing issue.

Before a few weeks ago, I was running Joplin Server via a Portainer/Docker container ontop of OMV6. However, I recently migrated to OMV7 and Docker Compose on a new Proxmox Server. I updated my Joplin Compose file to include my new IP address and that was all that was changed as I used the same database as on my old server as I just carried over my data drives. The mount remained the same (/srv/dev-disk-by-uuid-a914a7e5-3822-4cdb-a5e8-e8c7e3d13883/Joplin) as did my port and postgres version (13.1). It all appeared to work as after spinning up my container, I could log into the web interface at first and see my notes. They synced to my devices and I had all 2500 or so notes available on all my devices. Something however seems to have changed as my devices can no longer sync with my container and am getting a 'could not open file "base/16384/16469": No such file or directory' error when trying to sync. My database still exists on my server/container as I can see the files/folders. This issue occurs on my Laptop, Android Client and Desktop.

When I try to visit the container via it's address, I get the error on it's landing page: select "id", "user\_id", "auth\_code", "updated\_time", "created\_time" from "sessions" where "id" = $1 limit $2 - could not open file "base/16384/16420": No such file or directory

I have attached a copy of my log's but they seem to mostly just repeat the above error for various folders/files.

### Log file

[Joplin Log.txt](https://discourse.joplinapp.org/uploads/short-url/azR5JNDVFfvLHz5rfWUpkdQjJEP.txt) (53.6 KB)

---

<div class="post-metadata">

### Author: ![Steph](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/steph/32/17080_2.png) [@Steph](https://discourse.joplinapp.org/u/Steph)
#### Post date: [9 April 2025 11:17 UTC](https://discourse.joplinapp.org/t/syncing-error-could-not-open-file-no-such-file-or-directory/44781/2 "2025-04-09T11:17:28Z")

</div>

> [@UltraJon](#):
>
> I am wondering if you can help me with this syncing issue.

Have you try this ?

> [@How to fix synchronisation issues and start over](https://discourse.joplinapp.org/t/how-to-fix-synchronisation-issues/44410/1):
>
> If your app is not synchronising properly or something got corrupted and you want to start over, follow this guide. First, make a backup In all cases, the most reliable way to fix synchronisation is to start from a recent JEX backup of your notes. Having such backup also ensure you don't lose anything while you're trying to fix synchronisation. If one of your applications is in a good state and has all the data, you can create this JEX backup file from File =\> Export all =\> JEX Otherwise, you…

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/1/c/1c948e33314e232a0927789508474d8624f4270b.png) [@system](https://discourse.joplinapp.org/u/system)
#### Post date: [9 May 2025 11:18 UTC](https://discourse.joplinapp.org/t/syncing-error-could-not-open-file-no-such-file-or-directory/44781/3 "2025-05-09T11:18:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
