Joplin Server sync spins forever on DNS lookup failure
I have a Joplin Server instance running on my home LAN. It has an internal DNS name which is not resolvable on the public internet. This works fine when I am at home.
When I am on a public wifi connection, the Joplin Mac client fails to resolve the internal DNS name (as expected). But rather than quickly noticing this problem and giving up, Joplin gets stuck in an endless loop retrying. It also doesn't let me manually cancel the sync operation; it just gets stuck on "Cancelling..." when I click that button:
This consumes a lot of CPU/battery, it makes my Macbook warm to the touch, and it keeps trying to resync when I edit a note. It is not an ideal user experience. I would not want to keep Joplin running in this state while e.g. on an airplane with no charger.
I would suggest doing the following: if the OS indicates that the internet connection is good, and the DNS name fails to resolve, then Joplin should retry just a couple of times over the next 10 seconds or so. If it still can't resolve the host, indicate that to the user and wait for the user to manually re-initiate a sync operation (or for the network connection to change). Joplin should not be trying to auto-resync every few minutes if it knows that there's a DNS resolution issue.
The problem is trivially reproducible using the following settings:
My Joplin client is:
Joplin 2.12.17 (prod, darwin)
Client ID: 100cf434c70a424a8811e0715737793d
Sync Version: 3
Profile Version: 43
Keychain Supported: Yes
Revision: b9cb9e4
Outline: 1.3.1
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
This is also an issue with OneDrive sync.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Still an issue!
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Still an issue
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
At least on Ubuntu 23.10, this also happens when offline.