In some cases, the application may have troubles establishing the connection with our server due to network issues on your side. Please note that our app requires WebSocket connections.
To test if your network connection supports Websockets, please run the test on this website.
If the Websockets are identified, you'll see the following message:
If the result is different, it's most likely that there's something in your network that blocks WebSocket connections. If possible, please contact the network administrator and ask them to enable WebSocket connections on port 80 and 443 (SSL). They might be closed or filtered within your network. In order to establish a connection, these ports should be open for miro.com to access.
If you use a proxy that blocks WebSocket connections
If you use a proxy please ensure that you provide Miro with a by-pass. The following specifications will help.
- The proxy server must support WebSocket connections (HTTP/2).
- The proxy HTTP version should be set as 1.1.
- Source IP/host: Miro NAT IP is 126.96.36.199 (used for Atlassian integrations only).
- Source port: 80. 80 is used for users that access Miro through HTTP to direct them to HTTPS (blocking 80 is not recommended).
- Destination port: 443 (SSL). 443 is used for HTTPS.
- Protocol: HTTPS
- TLS: 1.2. (We’re hosted in AWS and use AWS Security Policies. When AWS and all our plugin partners start supporting 1.3. we will be able to migrate as well).
- The timeout value on the proxy server should be prolonged. It is most likely that your system waits around 60-90 seconds to connect. It would be best to prolong it to 120-180 seconds.
- The proxy server should not truncate the request and response headers. Please check if the Upgrade and Connection headers are proxied by the client.