Return Error When sync Cannot Reach Target

I ran into a new firewall issue at work today that prevented syncing.

But none of Joplin in Android, Linux desktop and Linux terminal returned an error.

Log.txt did show the error and it is not so hard to find log.txt. But even as a power-user developer it set me back 20 min (not including this documentation effort) trying to figure it out.

I’m set now for the future with this problem, but I think for getting Joplin to a bigger market share I think that a sync failure due to target not being accessible should return a useful message and not “complete.”

My Setup
Running Kubuntu KDE Plasma 19.10 as guest VM using VirtualBox 6.0 for Windows 10. I have both terminal, 0.150 (prod), and desktop (1.0.174 (prod, linux) running using separate Joplin profiles that target the same Nextcloud account. I’m using the Android app 1.0.312.

Thanks for all the great work.

It displays an error when sync fails, expect for certain network errors, like when the wifi is temperately off, because the issue goes away when the wifi is back on.

The error you got should have been displayed so there might be an issue with the way errors are filtered. Could you post the complete error message you got, so that I can disable filtering for it?

@laurent,

Below is the log. Thanks much.

019-12-20 11:45:07: "FetchError: request to https://us.hostiso.cloud/remote.php/webdav/.sync/ failed, reason: connect ECONNREFUSED 127.0.0.1:443
Code: ECONNREFUSED
FetchError: request to https://us.hostiso.cloud/remote.php/webdav/.sync/ failed, reason: connect ECONNREFUSED 127.0.0.1:443
    at ClientRequest.<anonymous> (/home/usergeorge/.joplin-bin/lib/node_modules/joplin/node_modules/node-fetch/index.js:133:11)
    at ClientRequest.emit (events.js:189:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:189:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)"
2019-12-20 11:45:07: "Operations completed: "
2019-12-20 11:45:07: "Total folders: 8"
2019-12-20 11:45:07: "Total notes: 84"
2019-12-20 11:45:07: "Total resources: 10"

@laurent,

Was the log I posted useful?

This type of error is temporary in general so that’s why it’s not displayed. If you had a firewall issue, doesn’t it mean that no application could access the internet?