Android App - won't sync

Support
1

Operating System: Android 10
Joplin Version: 1.4.11

I cannot sync to my WebDav based Joplin files. I am able to sync from my Mac but the app is saying that there is an error in username or password etc etc but they are exactly the same details as the ones that I have inputted in my Mac.

Screenshot_20201219-101850
Screenshot_20201219-1018501080×2400 541 KB
Screenshot_20201219-102633
Screenshot_20201219-1026331080×2400 235 KB

2

Hi, i think the URL is wrong or your phone can't resolve/reach the URL!

Network request failed

3

Hi, yes. Thanks for your response. That's why I'm confused. It's exactly the same details as the ones I have put in on my macOS Joplin App and it works fine. I've had Joplin on my phone for a while and it has always synced and I've never really had issues before so I'm even more confused!

4

can you open the URL in Safari/Browser on your phone?

5

Yes it does not then when I sign in it says that I don't have permissions. But can access my NAS web interface perfectly fine

6

Please post some more infos:

  • What kind of NAS?
  • Witch WebDAV Server
  • SSL: Yes/No
  • Selfsign certificate
  • The complete url tested in the browser, or only a part?
7

It's the Synology DS218j running DSM 7.0.
It is the WedDAV Server that comes baked into the OS
SSL: Yes
I tested both the complete and partial URL
In terms of Selfsign what do you want to know?

8

OK, with self-signed certificates I don't know how it behaves under Android.
I mean imported certificates into the trusted store are not recognized from Joplin?
Because when the SSL check does not work, the same error message appears.

9

The used servername in the URL is the same as the common name in the certificate ?

10

Yes the servername and common name on the certificate are the same too (It's Let's Encrypt)

11

Ok, than it's no self signed certificate.
All subcertificates included?

You can test this the follow way

  • Check the certificate file
  • use openssl openssl s_client -showcerts -servername <HOST> -connect <HOST>:<PORT>
  • use a web service like https://www.geocerts.com/ssl-checker
  • Or post the URL if this is publicly accessible and I check it
12

@scratchmaster2
You wrote by mistake "Yes it does not then when I sign in it says that I don't have permissions." This leaves some slack in the logic ... Can you please clarify ...

13

@ajay - yes sorry it's "Yes it does then I sign in it says that I don't have permissions."

@JackGruber here is the result of my check:

SSL Server Certificate

Common Name: [ADDRESS]

Issuing CA: Let's Encrypt Authority X3

Organization:

Valid: November 18, 2020 to February 16, 2021

Key Size: 2048 bits

Subject Alternative Names (SANs)

[ADDRESS]

Certificate Expiration

This certificate will expire in 59 days.

Certificate Common Name (CN) and Hostname Match?

The hostname ([ADDRESS]) matches the certificate and the certificate is valid.

DNS, etc.

[ADDRESS] resolves to [ADDRESS].
Server type: Apache

Certificate Chain Complete?

A valid Root CA Certificate could not be located, the certificate will likely display browser warnings.

Common Name: [ADDRESS]

Organization:

Valid: November 18, 2020 to February 16, 2021

Issuer: Let's Encrypt Authority X3

14

Ok, your certificate chain is not complete and this is a problem!

15

Ah - OK - Do you know how I can complete this? Also why has it never been a problem until now?

Thanks!

16

And you're sure that you're not using a firewall or VPN which blocks access to some DNS server or the like ? It could even be implicit or a default setting (not obvious during setup)

17

Normaly the Let's Encrypt certificate has a valid timespan for 90 days.
Has the problem possibly existed for a month?
Then this could have to do with the certificate renewal.

Normally, the fullchain certificate should be used from the certificats renewal process. But with the DSM7, I'm not sure if anything will go wrong.
You can adjust the certificate file by hand, but if you don't know what you are doing this can also go wrong and yor DSM website's no longer working.

18

Well I definitely don't know what I'm doing! :joy: Is there a tutorial or something?

19

DSM7 is a preview and all my diskstations are productive and on DSM6.2 so I can not tell you where to find the things on DSM7.

20

OK, I have analyzed the problem in more detail on a Syno with DSM7 and have opend a post in the DSM7 beta community.
WebDAV server use cert.pem instead of fullchain.pem

As a workaround you can do the following,

  1. Login as root
  2. cp /var/packages/WebDAVServer/target/etc/httpd/conf/extra/httpd-ssl.conf-cipher-webdav /var/packages/WebDAVServer/target/etc/httpd/conf/extra/httpd-ssl.conf-cipher-webdav.bak
  3. sed -i -e "s/cert.pem/fullchain.pem/g" /var/packages/WebDAVServer/target/etc/httpd/conf/extra/httpd-ssl.conf-cipher-webdav
  4. /var/packages/WebDAVServer/target/scripts/synowebdavserver_httpd_control.sh restart