# Can't connect with dropbox

**URL:** <https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171>\
**Category:** Support\
**Created:** [7 October 2026 03:31 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171 "2026-10-07T03:31:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dasyp](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/dasyp/32/30476_2.png) [@Dasyp](https://discourse.joplinapp.org/u/Dasyp)\
**Post date:** [7 October 2026 03:31 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171/1 "2026-10-07T03:31:56Z")

</div>

### Operating system

Windows

### Joplin version

3.7.18

### Desktop version info

Joplin 3.7.18 (prod, win32)

Устройство: win32, 12th Gen Intel(R) Core(TM) i5-12500  
Идентификатор клиента:  
Версия синхронизации: 3  
Версия профиля: 53  
Поддерживаемая связка ключей: Да  
Альтернативный идентификатор экземпляра: -  
Sync target: Dropbox  
Редактор: Свободный текст

Изменения: ce25482

Backup: 1.5.1  
Freehand Drawing: 4.3.0

### Sync target

Dropbox

### What issue do you have?

Due to OneDrive access issues, I wanted to set up synchronization via Dropbox, but I'm getting a certificate error (screenshot). How can I fix this?

### Screenshots

 ![joplin-dropbox error.jpg](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/6/4/64b813b6c63c54d741d67bd56bc5d6622007e2fc.jpeg)

---

<div class="post-metadata">

**Author:** ![dpoulton](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/dpoulton/32/29723_2.png) [@dpoulton](https://discourse.joplinapp.org/u/dpoulton)\
**Post date:** [7 October 2026 10:06 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171/2 "2026-10-07T10:06:00Z")

</div>

Are you on a company network? This error often occurs when a company is inserting its own private TLS certificates into the certificate chain so it can read and monitor your HTTPS traffic. As Joplin uses its own certificate authority store it does not recognise these certificates and the connection errors.

---

<div class="post-metadata">

**Author:** ![Dasyp](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/dasyp/32/30476_2.png) [@Dasyp](https://discourse.joplinapp.org/u/Dasyp)\
**Post date:** [7 October 2026 10:21 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171/3 "2026-10-07T10:21:23Z")

</div>

There are no such certificates within the company, and HTTPS traffic is not inspected. I am an administrator.

Could it be at the provider level?

---

<div class="post-metadata">

**Author:** ![dpoulton](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/dpoulton/32/29723_2.png) [@dpoulton](https://discourse.joplinapp.org/u/dpoulton)\
**Post date:** [7 October 2026 10:26 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171/4 "2026-10-07T10:26:09Z")

</div>

I doubt that it would be Dropbox as the certificate is "self-signed" and not by a recognised certificate authority. It would be a bit scary if somehow your ISP was doing this.

Could it be that your Anti-Virus / Internet Security software is responsible?

I do not know if this works for this kind of TLS error but there _is_ an option in the settings to "Ignore TLS Certificate errors"

**Tools \> Options \> Synchronisation \> Show Advanced Settings \> Ignore TLS Certificate errors**

---

<div class="post-metadata">

**Author:** ![Dasyp](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/dasyp/32/30476_2.png) [@Dasyp](https://discourse.joplinapp.org/u/Dasyp)\
**Post date:** [8 October 2026 02:36 UTC](https://discourse.joplinapp.org/t/cant-connect-with-dropbox/51171/5 "2026-10-08T02:36:15Z")

</div>

There is one (Ignore TLS certificate errors) for Nextcloud, but not for Dropbox.  
Disabling the antivirus seems to have helped. (Or switching to the English interface, lol)  
thank you.