Manage Flow connection issues

This article is for IT or network administrators in charge of managing an organization’s network. If you ever need a hand with troubleshooting connection issues, don’t hesitate to get in touch.


Desktop app

Older versions of the Flow for Mac/Windows apps can result in connection issues and even broken, out-of-date features. 
  • Be sure the desktop app is up-to-date. If you suspect that Flow is out of date, you can download the most recent version of the app here.
  • Review the system requirements to run the desktop app.

Network settings

To work effectively, Flow requires a persistent connection between our server and users’ apps or browsers. To do so, Flow uses WebSockets over port 443.
Proxies and firewalls can sometimes interrupt this connection. If someone using Flow can’t connect from a specific location, or if you’re consistently seeing the“Flow is not receiving real-time updates” error message in your account, you’ll need to adjust your proxy or firewall to keep the connection to Flow open. Here’s how:
  • Whitelist the following domains: 
    • app.getflow.com
    • api.getflow.com
    • socket.api.getflow.com
    • manage.getflow.com
    • secure.flowimageproxy.com
    • d11e1slvzlw6kj.cloudfront.net
  • Check if your proxy is running SSL decryption. If it is, the proxy must either support WebSockets, or you’ll need to exempt socket.api.getflow.com. 

Network environment

Certain software, security settings, and firewalls can interfere with Flow connections, like antivirus/anti-spyware software and ad-blockers. The best way to determine if these are behind your connection issues is to temporarily turn them off. This will let you troubleshoot your connection issue. If this fixes your issue, add socket.api.getflow.com to your software’s exemption list before re-enabling.

Still having trouble? If you’re unable to solves your connection issue using the above solutions, please get in touch

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.