# Network request failed error trying to sync Joplin iOS against NextCloud 24.0.2

**URL:** <https://discourse.joplinapp.org/t/network-request-failed-error-trying-to-sync-joplin-ios-against-nextcloud-24-0-2/26230>\
**Category:** Support\
**Created:** [28 June 2022 17:38 UTC](https://discourse.joplinapp.org/t/network-request-failed-error-trying-to-sync-joplin-ios-against-nextcloud-24-0-2/26230 "2022-06-28T17:38:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![platzh](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/platzh/32/4939_2.png) [@platzh](https://discourse.joplinapp.org/u/platzh)\
**Post date:** [28 June 2022 17:38 UTC](https://discourse.joplinapp.org/t/network-request-failed-error-trying-to-sync-joplin-ios-against-nextcloud-24-0-2/26230/1 "2022-06-28T17:38:46Z")

</div>

Dears,

I'm encountering the "Network request failed" error again when syncing Joplin on my iPad to my Synology NAS hosting NextCloud 24.0.2  
The WebDAV URL is [https://IP/nextcloud/remote.php/dav/Notizen/Joplin](https://IP/nextcloud/remote.php/dav/Notizen/Joplin).

Sync config check gives Network request failed error although user/passowrd/url is correct.

The versions I'm running are:  
Synology 7.1-42661  
Nextcloud 24.0.2  
iPadOS 15.5  
Joplin 12.8.1

Joplin on my Macbook works fine and syncs without problems.  
The WebDav-Page is reachable is reachable in the browser and gives the "This is the WebDAV interface..."-response

The problem only exists since my self-signed-certificate had to be renewed which I had done using openssl via cli on my mac and importing the certificates to the ipad and my SynologyNas.

I'm a bit stuck at the moment and am not sure where to look on and continue.

Log-Screenshot:

 ![IMG_B7619DDD368B-1](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/c/c368f4e7ee48392fab709a51426e016281871456.jpeg)

---

<div class="post-metadata">

**Author:** ![platzh](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/platzh/32/4939_2.png) [@platzh](https://discourse.joplinapp.org/u/platzh)\
**Post date:** [11 July 2022 15:02 UTC](https://discourse.joplinapp.org/t/network-request-failed-error-trying-to-sync-joplin-ios-against-nextcloud-24-0-2/26230/2 "2022-07-11T15:02:28Z")

</div>

So I managed to create a new self-signed-certificate and import it into the Diskstation. Joplin now works great again 😌

Most helpfull was this thread on Github: [Github-Link to the rescue](https://gist.github.com/fntlnz/cf14feb5a46b2eda428e000157447309) which I followed closely.

Only when creating the certificate using the csr I added the subjectAltName in form of an IP-Adress because I don't use a Domainname for my Diskstation in my local network.  
Like mentioned from one of the commentors on github; if you use more than one DomainName you should also include them in that way.

So instead of:

> openssl x509 -req -in mydomain.com.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out mydomain.com.crt -days 500 -sha256

I went with:

> openssl x509 -req -in IP.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out IP.crt -days 500 -sha256 -extfile \<(printf "subjectAltName=IP:xxx.xxx.xxx.xxx")

If you use Domainnames you will probably go with something like this:

> openssl x509 -req -in test.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out test.crt -days 500 -sha256 -extfile \<(printf "subjectAltName=DNS:firstDNSname,DNS:secondDNSname")

That did the trick for me.

I hope this helps anyone 🙂

---

<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:** [10 August 2022 15:03 UTC](https://discourse.joplinapp.org/t/network-request-failed-error-trying-to-sync-joplin-ios-against-nextcloud-24-0-2/26230/3 "2022-08-10T15:03:08Z")

</div>

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