It would be best to prolong it to 120-180 seconds. It is most likely that your system waits around 60-90 seconds to connect. The timeout value on the proxy server should be prolonged.When AWS and all our plugin partners start supporting 1.3. ( We’re hosted in AWS and use AWS Security Policies. 80 is used for users that access Miro through HTTP to direct them to HTTPS (blocking 80 is not recommended). Source IP/host: see the NAT IPs above (used for Atlassian integrations only).The proxy HTTP version should be set as 1.1.The proxy server must support WebSocket connections (HTTP/2).Please ensure that you provide Miro with a by-pass. Miro application IP addresses are dynamic. Note that the IP addresses are used only to reach out to the Atlassian systems in regard to the Jira-related integrations we have. You will need to add our static IP addresses to the allowlist as well. Please allowlist our domains and subdomains: If the Websockets are identified correctly but there are still issues establishing the connection, please contact Miro Support. In order to establish a connection, these ports should be open for Miro addresses to access (see addresses in the "If you use a Firewall" section below) They might be closed or filtered within your corporate network for security reasons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |