# All devices have stopped syncing

**URL:** <https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916>\
**Category:** Support\
**Created:** [18 June 2025 11:05 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916 "2025-06-18T11:05:39Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![clayt0n](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/clayt0n/32/26148_2.png) [@clayt0n](https://discourse.joplinapp.org/u/clayt0n)\
**Post date:** [18 June 2025 11:05 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/1 "2025-06-18T11:05:39Z")

</div>

### Operating system

Linux

### Joplin version

3.3.12

### Desktop version info

Joplin 3.3.12 (prod, linux)

Device: linux, Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz  
Client ID: 8db3c1e5bf484855a7cdd8d66e19429f  
Sync Version: 3  
Profile Version: 47  
Keychain Supported: No  
Alternative instance ID: -

Revision: 4d790b6

Backup: 1.4.3  
Freehand Drawing: 3.0.1  
Quick Move: 1.1.0  
Remove Images: 0.0.2  
Table Formatter Plugin: 1.2.1

### Sync target

WebDAV

### Editor

Markdown Editor

### What issue do you have?

Linux desktop and Android clients fail to sync with the error:

Completed: 18/06/2025 18:50 (3s)  
Last error: SyntaxError: Unexpected token '\<', "\<!doctype "... is not valid JSON

I am guessing this is a database corruption? Is there an easy way to recover?

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [18 June 2025 11:46 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/2 "2025-06-18T11:46:27Z")

</div>

The problem is not a database corruption, otherwise it would only break 1 client (device). Who is your WebDAV provider and are you on a free or paid plan?

There have been reported issues where WebDAV providers (eg. TabDigital) particularly on free plans have made changes which have caused the data on the server to become corrupted.

Also, if you could include a section of the log file which includes that error, it may give additional details

---

<div class="post-metadata">

**Author:** ![clayt0n](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/clayt0n/32/26148_2.png) [@clayt0n](https://discourse.joplinapp.org/u/clayt0n)\
**Post date:** [19 June 2025 09:15 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/3 "2025-06-19T09:15:21Z")

</div>

> [@](#):
>
> The problem is not a database corruption, otherwise it would only break 1 client (device). Who is your WebDAV provider and are you on a free or paid plan?

This Webdav is running on my own VM which I manage, and has been running many, many moons without problem or changes except occasional OS updates. I am seeing the last Apache update on the server happened November of last year, and if that were the cause of breakage, I would have noticed a long time ago. Whatever broke, broke much more recently.

> [@](#):
>
> Also, if you could include a section of the log file which includes that error, it may give additional details

That was instructive.... I could not find logs in the Linux Joplin, but on Android is is clear that DNS is failing, and this seems to be what a DNS failure looks like on Joplin.

On Linux I swapped the domain name out and put the IP address, and it now syncs fine. However, not on Android. The Android log now reports a "Network request failed" error. But since this exact same WebDAV URL with an IP address works fine in Linux Joplin, clearly the server has no problem with this arrangement. It seems to be an Android thing.

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [19 June 2025 09:32 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/4 "2025-06-19T09:32:07Z")

</div>

Can you post a a section from the Android log about the new error you are getting please?

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [19 June 2025 23:33 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/5 "2025-06-19T23:33:49Z")

</div>

Also what version is your Android app? If you're using Nextcloud, there was a fix which was included in v3.3.1

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [20 June 2025 00:10 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/6 "2025-06-20T00:10:29Z")

</div>

> [@mrjo118](#):
>
> Can you post a a section from the Android log about the new error you are getting please

Having a search on the forum for the network request failed error seems to indicate an error that gives no additional information in the logs, so I'm now not really hopeful that would give any additional context to the situation.

Despite that you are able to get it to work on Linux now, the fact that you needed to change the connection to use your ip to get it to work suggests something with your network configuration has changed. Network setup is not really something I can help you with as I don't have knowledge in that area.

I did find this page which gives some detail about how you might need to configure your network for self hosting though. You could have a look at that and see if it highlights anything you need to configure differently:

> [@Network requests failed error with Nextcloud 20](https://discourse.joplinapp.org/t/network-requests-failed-error-with-nextcloud-20/12734/23):
>
> OK, I don't know your network. I'll just assume it's set up something like this. [grafik] 192.168.1.1 192.168.1.10 192.168.1.50 red) To reach the nextcloud.host.mydomain.fr from the WAN, you have configuard a NAT. WANIP:445 -NAT-\> 192.168.1.10:445 on your WAN interface green option 1) You have configuard nextcloud.host.mydomain.fr to 192.168.1.10 on your PiHole Then all clients who have the PiHole as DNS server in the internal network can reach nextcloud.host.mydomain.fr on 192.168.1.10 g…

---

<div class="post-metadata">

**Author:** ![clayt0n](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/clayt0n/32/26148_2.png) [@clayt0n](https://discourse.joplinapp.org/u/clayt0n)\
**Post date:** [20 June 2025 08:32 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/7 "2025-06-20T08:32:12Z")

</div>

> 06-20T16:17:12: Synchronizer: Total folders: 87  
> 06-20T16:17:12: Synchronizer: Total notes: 966  
> 06-20T16:17:12: Synchronizer: Total resources: 51  
> 06-20T16:17:12: Synchronizer: Operations completed:  
> 06-20T16:17:12: Synchronizer: Sync: finished: Synchronisation finished [1750407406375]  
> 06-20T16:17:12: Synchronizer: TypeError: Network request failed  
> TypeError: Network request failed  
> at anonymous (address at index.android.bundle:1:325626)  
> at apply (native)  
> at anonymous (address at index.android.bundle:1:293332)  
> at \_callTimer (address at index.android.bundle:1:292630)  
> at callTimers (address at index.android.bundle:1:294398)  
> at apply (native)  
> at \_\_callFunction (address at index.android.bundle:1:156006)  
> at anonymous (address at index.android.bundle:1:154311)  
> at \_\_guard (address at index.android.bundle:1:155267)  
> at callFunctionReturnFlushedQueue (address at index.android.bundle:1:154269)  
> 06-20T16:16:56: SearchEngine: Updated FTS table in 24ms. Inserted: 0. Deleted: 0  
> 06-20T16:16:56: Updating items\_normalized from {"updated\_time":0,"id":""}  
> 06-20T16:16:56: SearchEngine: Updating FTS table...  
> 06-20T16:16:50: RevisionService: maintenance: Done in 137ms

is the relevant chunk from the Android log. Note that Android Joplin is reporting sync "finished" / no errors despite not actually connecting to the server, which strikes me as bug all by itself. The only way you would know something went astray (other than noticing that nothing actually synced) is to dig up the log.

So what changed is simply that I did not renew the domain name, as I no longer need it, and now I actually wish to use just the IP address in the WebDAV URL, as I have no other need for a domain name on this VM. There is no NextCloud or "cloud" anything here, this is just Apache configured to provide WebDAV.

Android version is

> Joplin Mobile 3.3.10 (prod, android)
> 
> Device: android  
> Client ID: 5694367ba17641aab275127d5fb943d9  
> Sync Version: 3  
> Profile Version: 47  
> Keychain Supported: No  
> Alternative instance ID: -
> 
> Revision: b0d888ee7
> 
> Android API level: 33  
> WebView version: 135.0.7049.100  
> WebView package: com.android.webview  
> FTS enabled: 1  
> Hermes enabled: 1

The situation is pretty simple: Linux Joplin succeeds in connecting to and syncing with WebDAV using a URL that contains an IP address instead of a domain name. Android fails to connect to the same server with the same URL. I think this should either work on all devices, or not work on all devices.

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [20 June 2025 09:51 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/8 "2025-06-20T09:51:08Z")

</div>

As suspected, the log for that error gives no helpful information.

This is an AI response from Google asking "joplin webdav does not work ip address"

 ![Screenshot_20250620_104856_Chrome](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/9/d/9d5fbe068dc527f3ab8a664051bd87a6d44ca846.jpeg)

There may be similar security restrictions / policies on Android which prevents you using an ip address to connect to your server with Joplin

---

<div class="post-metadata">

**Author:** ![mrjo118](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrjo118/32/23404_2.png) [@mrjo118](https://discourse.joplinapp.org/u/mrjo118)\
**Post date:** [20 June 2025 10:14 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/9 "2025-06-20T10:14:35Z")

</div>

Both the IOS and Android app use React Native, so there may be restrictions with that:

> <https://github.com/laurent22/joplin/issues/10420>
>
> \### Operating system
> 
> iOS
> 
> \### Joplin version
> 
> ios 12.14.8
> 
> \### Desktop version …info
> 
> \_No response\_
> 
> \### Current behaviour
> 
> Joplin won't sync on target webdav server on iOS client showing \`Network request failed\`, while other desktop versions work normally. 
> 
> 1. I double checked webdav user-password configs and I'm sure all information are correct.
> 2. I tried to uninstall and reinstall joplin on my iphone and the error remains.
> 3. My webdav service is a self-hosted nginx one and I use plain http and ip address for years as my sync target, it works well just until today. 
> 4. just FYI, my mac client version is 2.13.12, my windows10 client version is 2.13.13, again, they are still functional under the same specs.
> 
> 
> 
> 
> 
> 
> \### Expected behaviour
> 
> iOS client can sync normally again.
> 
> \### Logs
> 
> !\[IMG\_1769\](https://github.com/laurent22/joplin/assets/39869906/185b94c1-0ba3-4b36-be81-3cd5da2865e1)

A couple of things to consider / try:  
Make sure the url for your ip address uses https:// and also under advanced settings on the synchronization settings screen, you could try ticking the ignore tls certificate errors option

---

<div class="post-metadata">

**Author:** ![clayt0n](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/clayt0n/32/26148_2.png) [@clayt0n](https://discourse.joplinapp.org/u/clayt0n)\
**Post date:** [20 June 2025 10:41 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/10 "2025-06-20T10:41:07Z")

</div>

> [@mrjo118](#):
>
> ticking the ignore tls certificate errors option

seems to have done the trick!! Good catch, thanks!

Propagating TLS errors up to the UI would be very helpful here, if possible.

---

<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:** [20 July 2025 10:41 UTC](https://discourse.joplinapp.org/t/all-devices-have-stopped-syncing/45916/11 "2025-07-20T10:41:13Z")

</div>

Closed on 20 July 2025 10:41 UTC

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