Ad Space — Top Banner

Couldn't Establish Secure Connection

Dropbox Software

Severity: Minor

What Does This Error Mean?

Dropbox shows 'Couldn't establish a secure connection' when its desktop app cannot complete a TLS handshake with Dropbox servers.
The error is downstream of the network — Dropbox itself is fine 99% of the time it appears.
Cause is almost always a proxy, an antivirus that intercepts HTTPS, or an outdated client that doesn't support modern TLS ciphers.
The fix is to identify which of those is in the way and either work around it or update.

Affected Models

  • Dropbox desktop on Windows 10 and 11
  • Dropbox desktop on macOS
  • Dropbox desktop on Linux
  • Dropbox running behind corporate or school networks

Common Causes

  • Antivirus or endpoint protection inspecting HTTPS traffic
  • Corporate proxy not configured to allow Dropbox endpoints
  • PAC file pointing to a stale proxy server
  • Old Dropbox client version with deprecated TLS support
  • Wrong system clock — TLS rejects certificates with bad timestamps

How to Fix It

  1. Check the system clock.

    Open Settings → Time & Language (Windows) or System Settings → General → Date & Time (macOS).
    Make sure 'Set time automatically' is on.
    If the clock is more than 5 minutes off, TLS rejects the certificate and you see this exact error.
    Wrong-time PCs are the single most common cause.

  2. Pause antivirus HTTPS scanning.

    Open your antivirus dashboard and find the web protection or HTTPS scanning option.
    Pause it for two minutes and retry Dropbox.
    If it works, your AV is intercepting Dropbox's traffic with a substitute certificate that Dropbox refuses.
    Add Dropbox to the AV's exclusion list — most vendors document this.

  3. Test from another network.

    Tether to your phone or use mobile data.
    If Dropbox connects fine, your home or office network is the problem — proxy, firewall, or DNS.
    If it fails everywhere, the problem is on the PC and you can skip the network steps.

  4. Update or reinstall Dropbox.

    Old versions used TLS 1.0 / 1.1 which Dropbox servers no longer accept.
    Visit dropbox.com/install and download the latest version.
    Install over the existing one — your files and settings are preserved.
    This single step fixes a meaningful share of persistent secure-connection errors.

  5. Check proxy settings.

    Windows: Settings → Network & Internet → Proxy.
    If 'Use a proxy server' is on but you're not on a corporate network, turn it off.
    If you are on a corporate network, ask IT to allow client.dropbox.com, dl.dropboxusercontent.com, and notify.dropbox.com through the proxy.

Frequently Asked Questions

Why does the website work but the app doesn't?

Browsers ship with their own up-to-date TLS stack.
The Dropbox desktop app uses the operating system's TLS — which on older Windows builds may not support the cipher suites Dropbox now requires.
That's why dropbox.com loads fine in your browser while the app shows this error.