Your are disconnected from Trello

Question

Hi,

I have this message and so do my team. Trello doesn't show as being down.

Carlos Garcia Navarro · Answer

Hi @Leanna Hall ,

* Reload Trello after confirming your internet connection works. Long-open tabs and computers waking from sleep can lose their connection.
* Have one person test using a phone’s cellular connection or hotspot. If that works, it points toward your shared network, VPN, or proxy.
* Try another browser or a private window. If the problem occurs only on your company network, ask IT to check Trello’s firewall requirements. Trello documents firewall and VPN conflicts as possible causes.

Anwesha Pan · Answer

Hi @Leanna Hall

Since this is happening across the team, the issue is almost certainly shared across your network or security setup. Here are few steps to identify the cause and resolve it:

* VPN, Firewall, or Proxy: Enterprise firewalls, proxies, and security tools (such as Zscaler, Cisco Umbrella, Netskope, Fortinet, or Palo Alto) frequently inspect, throttle, or terminate long-lived WebSocket connections.* You or anyone of your team member can retry by disconnecting from the corporate VPN or open the board in your phone using home Wi-Fi.* If Trello connects immediately on a regular network, your corporate IT/network security team needs to whitelist Trello's real-time endpoints.

* Atlassian access/ SSO session expiration: If your organization uses Atlassian Access, SAML/SSO, or enforced session policies:* Try to log out completely, clear browser session cookies for trello.com and id.atlassian.com, and log back in.

* Few other options to consider:* Hard Refresh: Press Cmd + Shift + R (Mac) or Ctrl + F5 (Windows) to force a clean re-establishment of the socket session.
* Test an Incognito / Private Window: This rules out interference from ad-blockers, anti-tracking extensions (like Privacy Badger or uBlock Origin), or corrupted browser caches.
* Desktop App vs. Web Browser: If you are using the desktop application, test opening the board in a browser (Chrome/Edge/Safari) or vice versa. The desktop app can hold stale socket states longer than the browser.

I hope this helps & resolves your issue. 🙂

Thanks,

Anwesha