No sync on webDAV after upgrade to 1.0.178


after upgrading to 1.0.178 on a Mac the sync on webDAV failed. Worked before with 1.0.175. Login data are ok and working on 3 other devices. Any idea whats happening?

request to https://[…] failed, reason: write EPROTO 140471234529928:error:100000f0:SSL routines:OPENSSL_internal:UNSUPPORTED_PROTOCOL:…/…/third_party/boringssl/src/ssl/ (Code EPROTO)

We need the full error with context

Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:

request to https://[…] failed, reason: write EPROTO 140214707002712:error:100000f0:SSL routines:OPENSSL_internal:UNSUPPORTED_PROTOCOL:…/…/third_party/boringssl/src/ssl/ (Code EPROTO)

1 Like

Same problem after upgrading to 1.0.78 on windows 10. 2 different windows 10 machines with latest win 10 installation. No PW changes. Mobile iOS client works.

pls. fix

Letzte Fehlermeldung: FetchError: request to https://… failed, reason: write EPROTO 1445490152:error:100000f0:SSL routines:OPENSSL_internal:UNSUPPORTED_PROTOCOL:…/…/third_party/boringssl/src/ssl/

at ClientRequest. (C:\Program Files\Joplin\resources\app.asar\node_modules\node-fetch\index.js:133:11)
at ClientRequest.emit (events.js:203:13)
at TLSSocket.socketErrorListener (_http_client.js:399:9)
at TLSSocket.emit (events.js:203:13)
at errorOrDestroy (internal/streams/destroy.js:107:12)
at onwriteError (_stream_writable.js:439:5)
at onwrite (_stream_writable.js:460:5)
at internal/streams/destroy.js:49:7
at TLSSocket.Socket._destroy (net.js:595:3)
at TLSSocket.destroy (internal/streams/destroy.js:37:8)"

posted below

just downgraded to 1.0.175 and WebDAV sync started working. So it is an 1.0.178 issue