Sync setup for Dropbox

Operating system

Windows

Joplin version

3.0.15

Desktop version info

Joplin 3.0.15 (prod, win32)

Client ID: eb18e93c0e884544819a508b898f3e59
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 598677b

Backup: 1.4.1

Sync target

Dropbox

What issue do you have?

I'm trying to initially set up Synchronaisation with Dropbox, using the Sync Wizard.
I get to the Dropbox API and get a code, but when click Submit, after copy/pasting the Dropbox auth code to Koplin, I immediately and consistently get the error:
Could not authorise application:
request to https://api.dropboxapi.com/oauth2/token failed, reason: getaddrinfo: ENOTFOUND api.dropboxapi.com
Please try again
I've seen similar message posted in various Forums, but they seem to suggest that the error is temporary. It doesn't appear to be temporary for me, though.

Hello dmh, welcome to the forum !
Just in case : have you try with the last Joplin version (3.3.12) ?

Steph,

Thank you, and thanks for answering my question.
No, I'm on version 3015, and I get a "getaddrinfo ENOTFOUND objects.joplinusercontent.com" error when I try to check for updates.
So, I'd guess from that it is a more fundamental issue that I'm deali9ng with, and not just an issue with the Joplin/Dropbox interface; would you agree?

Cheers,
dave

Check your firewall settings. Maybe inbound/outbound connections have been set to blocked for the Joplin app.

You could also try manually upgrading by download the latest Joplin from the website and then install the new version on top of the existing installation

Since the the 3.3.7 a firewall warning on startup is supposed to be fix (#12176 by @personalizedrefrigerator)... I don't know if it's the same you are thinking about... ?

You should try the last version:

Of course "just in case" don't forget to backup your joplin datas before !


You can also backup with .jex by yourself:

I did not know there was a recent fix related to this, but yes that issue may have been the cause.

If the OP did get this popup for Joplin and accidentally denied access to it, then it may have created a rule for the Windows firewall. In which case the rule might need to be deleted / changed to allow connections, even after upgrading to the latest version

1 Like