NextCloud / WebDAV Cert Error

I’m sync’ing against NextCloud 18.0.4 with:

  • Joplin v1.0.216 for Windows 10
  • Joplin v1.0.216 for Linux on Ubuntu 18.04.3 TLS
  • Joplin v1.0.329 for Android 10
  • Joplin v1.0.216 for MacOS 10.15.4 (Catalina)

Starting within the past couple of days I’m now seeing a sync error on other than Android:

Completed: 2020-06-02 09:34

Last error: FetchError: request to https colon slash slah myserver/remote.php/webdav/joplin/.sync/ failed, reason: certificate has expired

This happens with both sync types “Nextcloud” and “WebDAV”.

Again, this issue does not manifest on Android.

  • My NextCloud clients for Mac and Windows work without error, other WebDAV clients (e.g., WebDrive) work without issue.
  • Browser-based connections to the NextCloud instance work w/o issue and correctly report that the cert expires October 8, 2021.
  • All of the cert checkers I’ve tried (e.g., https://www.digicert.com/help/) report that the cert is valid and correctly installed.

I can’t post the debug output because it puts me over 4 links, preventing me from posting at all. That said, I see nothing in the console output that appears to be related to the issue.

On a side note, I am able to work around the error by checking the Ignore TLS certificate erros box, but that’s (obviously) not a good long-term solution.

I was also able to work around the issue by sync’ing to a local folder and throwing that under NextCloud sync. In some testing this afternoon, it even works with the Android devices using Joplin’s Nextcloud sync; updates go both ways regardless.

There are actually arguments for doing it this way, like all the time instead of a native Joplin sync, and it’s more palatable than ignoring TLS errors, but it would still be nice to see Joplin behave or identify the underlying cert issue (if there really is one).

FYI: If you use inline code or a code block you can use as many links as you want.

1 Like

Hi,
Same issue identified in my environment within the past 24 hours for webdav sync to OwnCloud:
IPad and Android device are happily syncing.
On Windows10, portable as well as installed Joplin versions (1.0.201 & 1.0.216) yield “certifcate has expired”.
Browser acces to the same OwnCloud instance working. Certificate valid.
Tried on three different machines with different configurations.
Let me know in case I can be of further assistance.
Stay safe

I am not able to reproduce this issue. I’m using git master (commit hash f4092c08) on macOS 10.14.6 and just synced to a Nextcloud 17.0.6.

Any chance there’s more information in the debug log?

Environment: prod
<much startup output omitted to bring character count down to postable limit>
    step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
initNoteState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:43
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:137
fulfilled @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
fulfilled @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
loadNote @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:129
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:143
commitHookEffectList @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:19986
commitPassiveHookEffects @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:20016
callCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:347
invokeGuardedCallbackDev @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:397
invokeGuardedCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:454
flushPassiveEffectsImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22868
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushPassiveEffects @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22841
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22419
scheduler_flushTaskAtPriority_Normal @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:436
flushTask @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:482
flushWork @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:607
performWorkUntilDeadline @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:231
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(NoteTextViewerComponent), Connect(NoteToolbar), Connect(ToolbarComponent)
printWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11686
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
dispatchAction @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:15816
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:70
fulfilled @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
initNoteState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:43
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:137
fulfilled @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
fulfilled @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:5
Promise.then (async)
step @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:7
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:8
__awaiter @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:4
loadNote @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:129
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useFormNote.js:143
commitHookEffectList @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:19986
commitPassiveHookEffects @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:20016
callCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:347
invokeGuardedCallbackDev @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:397
invokeGuardedCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:454
flushPassiveEffectsImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22868
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushPassiveEffects @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22841
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22419
scheduler_flushTaskAtPriority_Normal @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:436
flushTask @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:482
flushWork @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:607
performWorkUntilDeadline @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:231
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(ConfigScreenComponent)
printWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11680
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
onStateChange @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:222
notify @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
dispatch @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\redux\lib\createStore.js:186
generalMiddleware @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:425
generalMiddleware @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\app.js:284
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:362
dispatch @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:541
click @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\app.js:644
apply @ callbacks-registry.ts:45
(anonymous) @ remote.js:292
(anonymous) @ remote.js:272
emit @ events.js:210
onMessage @ init.ts:50
Show 2 more frames
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(ConfigScreenComponent)
printWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11686
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
scheduleUpdateOnFiber @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21431
enqueueSetState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:13100
Component.setState @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react\cjs\react.development.js:325
onStateChange @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:222
notify @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:30
notifyNestedSubs @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\utils\Subscription.js:69
onStateChange @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-redux\lib\components\connectAdvanced.js:219
dispatch @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\redux\lib\createStore.js:186
generalMiddleware @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:425
generalMiddleware @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\app.js:284
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:362
dispatch @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\BaseApplication.js:541
click @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\app.js:644
apply @ callbacks-registry.ts:45
(anonymous) @ remote.js:292
(anonymous) @ remote.js:272
emit @ events.js:210
onMessage @ init.ts:50
Show 2 more frames
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(EncryptionConfigScreenComponent)
printWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11680
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
discreteUpdates$1 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21677
discreteUpdates @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:2359
dispatchDiscreteEvent @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:5979
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Connect(EncryptionConfigScreenComponent)
printWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11494
lowPriorityWarning @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11513
ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11686
flushRenderPhaseStrictModeWarningsInDEV @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:23134
commitRootImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22428
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
commitRoot @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:22414
runRootCallback @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21554
(anonymous) @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11353
unstable_runWithPriority @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\scheduler\cjs\scheduler.development.js:643
runWithPriority$2 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11305
flushSyncCallbackQueueImpl @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11349
flushSyncCallbackQueue @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:11338
discreteUpdates$1 @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:21677
discreteUpdates @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:2359
dispatchDiscreteEvent @ C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\react-dom\cjs\react-dom.development.js:5979
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\gui\NoteEditor\utils\useMessageHandler.js:29 Got ipc-message: noteRenderComplete [undefined]
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\JoplinServerApi.js:120 curl -v -X POST -H "Authorization: Basic amVmZnk6ZGM4Mjg1YjcxIw==" -H "Content-Type: application/json" --data '{"webDavUrl":"https://bigsheeva.thatonedomain.com/remote.php/webdav/j2"}' https://bigsheeva.thatonedomain.com/index.php/apps/joplin/api/sync_targets
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\components\shared\config-shared.js:99 Saving sync.target 5
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\components\shared\config-shared.js:99 Saving sync.5.path https://bigsheeva.thatonedomain.com/remote.php/webdav/j2
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\components\shared\config-shared.js:99 Saving sync.5.syncTargets {https://bigsheeva.thatonedomain.com/remote.php/webdav/j2: {…}}
C:\Users\jeffro\AppData\Local\Programs\Joplin\resources\app.asar\lib\components\shared\config-shared.js:99 Saving net.ignoreTlsErrors false

I posted the output, but Askimet hid it.

I had to blockquote it to get past the 4-link limit, and I had to drop several thousand characters to get around the 32K character post limit.

I don’t see anything in the output related to the error. Is there another log where we can look?

Don’t know if it helps, but here is what I could find in “log.txt”:

2020-06-04 16:21:01: "Profile directory: H:\bin\JoplinPortable/JoplinProfile"
2020-06-04 16:21:01: "Trying to load 1 master keys..."
2020-06-04 16:21:01: "Loaded master keys: 1"
2020-06-04 16:21:01: "ResourceFetcher: Auto-add resources: Mode: always"
2020-06-04 16:21:01: "ResourceFetcher: Auto-added resources: 0"
2020-06-04 16:21:01: "Trying to load 1 master keys..."
2020-06-04 16:21:01: "Loaded master keys: 1"
2020-06-04 16:21:01: "Scheduling sync operation...", "10000"
2020-06-04 16:21:01: "Trying to load 1 master keys..."
2020-06-04 16:21:01: "Loaded master keys: 1"
2020-06-04 16:21:01: "Scheduling sync operation...", "10000"
2020-06-04 16:21:01: "Trying to load 1 master keys..."
2020-06-04 16:21:01: "Loaded master keys: 1"
2020-06-04 16:21:01: "Scheduling sync operation...", "10000"
2020-06-04 16:21:01: "Scheduling sync operation...", "10000"
2020-06-04 16:21:01: "RevisionService::runInBackground: Starting background service with revision collection interval 600000"
2020-06-04 16:21:02: "DecryptionWorker: starting decryption..."
2020-06-04 16:21:02: "DecryptionWorker: completed decryption."
2020-06-04 16:21:05: "RevisionService::maintenance: Starting..."
2020-06-04 16:21:05: "RevisionService::maintenance: Service is enabled"
2020-06-04 16:21:05: "RevisionService::collectRevisions: Created revisions for 0 notes"
2020-06-04 16:21:05: "RevisionService::maintenance: Done in 115ms"
2020-06-04 16:21:10: "Scheduling sync operation...", "0"
2020-06-04 16:21:10: "Preparing scheduled sync"
2020-06-04 16:21:10: "Starting scheduled sync"
2020-06-04 16:21:11: "SearchEngine: Updating FTS table..."
2020-06-04 16:21:11: "SearchEngine: Updated FTS table in 3ms. Inserted: 0. Deleted: 0"
2020-06-04 16:21:31: "ResourceService::indexNoteResources: Start"
2020-06-04 16:21:31: "FetchError: request to https://ssl-account.com/removed/remote.php/webdav/data/JoplinSync/.sync/ failed, reason: certificate has expired
Code: CERT_HAS_EXPIRED
FetchError: request to https://ssl-account.com/removed/remote.php/webdav/data/JoplinSync/.sync/ failed, reason: certificate has expired
    at ClientRequest.<anonymous> (C:\Users\removed\AppData\Local\Temp\1cME4IKk3GCtYL3vlfVJy8PiDAY\resources\app.asar\node_modules\node-fetch\index.js:133:11)
    at ClientRequest.emit (events.js:210:5)
    at TLSSocket.socketErrorListener (_http_client.js:406:9)
    at TLSSocket.emit (events.js:210:5)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)"
2020-06-04 16:21:31: "Operations completed: "
2020-06-04 16:21:31: "Total folders: 12"
2020-06-04 16:21:31: "Total notes: 126"
2020-06-04 16:21:31: "Total resources: 152"
2020-06-04 16:21:31: "There was some errors:"
2020-06-04 16:21:31: "FetchError: request to https://ssl-account.com/removed/remote.php/webdav/data/JoplinSync/.sync/ failed, reason: certificate has expired
Code: CERT_HAS_EXPIRED
FetchError: request to https://ssl-account.com/removed/remote.php/webdav/data/JoplinSync/.sync/ failed, reason: certificate has expired
    at ClientRequest.<anonymous> (C:\Users\removed\AppData\Local\Temp\1cME4IKk3GCtYL3vlfVJy8PiDAY\resources\app.asar\node_modules\node-fetch\index.js:133:11)
    at ClientRequest.emit (events.js:210:5)
    at TLSSocket.socketErrorListener (_http_client.js:406:9)
    at TLSSocket.emit (events.js:210:5)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)"
2020-06-04 16:21:31: "ResourceService::indexNoteResources: Completed"
2020-06-04 16:21:31: "ResourceService::deleteOrphanResources:", "[]"
2020-06-04 16:21:32: "DecryptionWorker: starting decryption..."
2020-06-04 16:21:32: "DecryptionWorker: completed decryption."

Since it seems like this issue is limited to Windows it may make sense if we try to find out whats common in our environments. Here are the possible culprits I can think of on my system:
Windows 10 Prof. x64, build 18362.836
Bitdefender Total Security, build 24.0.24.131

Cheers

I see the same issue on the following as well, so the issue doesn’t appear to be limited to Windows:

  • Ubuntu 18.04.3 TLS
  • MacOS 10.15.4 (Catalina)

To directly answer your question, I’m running Windows 10 Pro for Workstations 1909 b18363.778.

And that all said, what the heck is “ssl-account.com”? I wonder if I have a DNS issue?

I’ve ruled out DNS.

I started by taking my phone off the wi-fi, turning on its hotspot function, and then connecting my Windows machine to that. Same issue using Sprint/T-Mobile.

I then put the Windows machine back on the local network and overrode public DNS (Cloudflare) with an entry for my NextCloud instance on my local DNS server.

Evo just removed his server name.

1 Like

I still do not see anything in the logs that would explain this. Are you sure that you don’t run this from a network that uses something like a transparent proxy that decrypts and encrypts your traffic on the fly? Some companies to that in their offices and/or VPN.

Does this happen everywhere (home, office, VPN, Starbucks, …)? It’s hard to narrow it down, because I can’t reproduce it. Maybe @laurent has an idea.

At this point I’d look at the traffic between Joplin and your server using wireshark or something similar.

Hi,
Updates:

  1. Disregard the URL in my logs. ssl-account.com is the certificate proxy of my webspace provider. I left it in, in case anyone wants to check their certificate. The rest of the URL is anonymised as tessus rightly suspected
  2. Apologies I missed that jeffro is facing this issue outside of Microsoft as well, so…
  3. … I have just reactivated my outdated ubuntu partition for a fresh install of 1.0.216 on Linux - unfortunately I could reproduce the “certificate has expired” issue immediately.
  4. I am on my own network without proxy, connected into the DSL infrastructure of my provider eircom (Ireland). My alternative connection is via 4G through Three Ireland. Both Ipad and Android phone continue to sync seamlessly through these connections.
  5. I installed wireshark but haven’t used it in ages and was not able to get it to listen to my interfaces yet as a result (sry for that).
  6. Since this thread is not causing more people to report the same issue, an edge case (or a malware infection?) may be at hand that only occurred since the beginning of this month (at least in my case).

I understand that there is not much that can be done if the issue cannot be reproduced. To remedy this I can offer a remote session via Discord in case you @tessus or @laurent would like to investigate this on my machine.

Thank you very much for your time and effort.

All the best and stay safe

Am having exactly the same issue on my Windows system (same error messages). My issue startet on 01.06.20 (June 1st). On 29.05.20 I upgraded from 1.0.124 to 1.0.126, but was happily syncing on that day afterwards (based on 1.0.126). On 01.06.20 when I started Joplin desktop the issue occured for the first time.

The certificate is not exipred (am using a signed certificate valid for another 1.5 years). No proxy in play as well. Did not change anything on the Nextcloud server (no Joplin app upgrade or something).

I set up Nextcloud but met with similar (not the same) errors. Might because of the needed “Joplin web app” plugin for Nextcloud was experimental. I abandoned the Nextcloud plan.

I’m rather busy these days (started a new job and this weekend I’m mostly without computer) and the time difference doesn’t make it easier. But maybe somebody else can have a look.

Hi,

@tessus - Congratulations and good luck with the new job - I can imagine that your next couple of weeks will be exhausting (and hopefully rewarding at the same time), so don’t let yourself get side tracked by us.

I have managed a network capture in the meantime and since reports from more users are coming in, it may be more efficient to move the topic to the issue tracker. I intend to restest against .218 before creating a new ticket, then post the link here, so we can close this thread.

Stay safe

1 Like

Ticket created: