GoRetro is an HTML5 web application that works in your browser. Occasionally GoRetro functions may have trouble performing when GoRetro is not allowed access. This can happen due to issues or limitations applied to your network connection or the environment that you use. If you are having trouble connecting to GoRetro see the steps below for potential solutions.
WebSockets
The GoRetro application - specifically the board page - requires WebSocket connections. If you're having issues opening your boards but the dashboard and the team pages open as expected this might mean that your connection does not support WebSockets.
How do I test my connection?
There are 2 ways to test your connection.
Open your browser's developer console. If you are using Chrome, right-click and choose inspect. The developer console will show up, then choose the console tab. If the WebSockets are blocked, this error will appear in your console: "Error during WebSocket handshake".
Open this website, if the Websockets are identified, you'll see the message in the image below. If the result is different, it's most likely that there's something in your network that blocks WebSocket connections.
If the tests indicate your network blocks the Websockets, try the following:
Use a different network connection
Use or turn off a VPN
If you use a corporate connection contact your network administrator and ask them to enable the WebSocket connections on port 80 and 443 (SSL). They might be closed or filtered within your corporate network for security reasons. In order to establish a connection, these ports should be open for GoRetro addresses to access (see addresses in the "If you use a Firewall" section below)
If the Websockets are identified correctly but there are still issues establishing the connection, please contact GoRetro Support.
What should I do next?
Please reach out to your company's IT team with the details below 👇
If you use a Firewall
Please allowlist our domains and subdomains: goretro.ai, app.goretro.ai *.goretro.ai
You will need to add our static IP addresses to the allowlist as well. :
34.107.31.165
34.107.157.208
34.98.127.7
34.107.136.189
If you use a proxy
Please ensure that you provide GoRetro 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: see the NAT IPs above (used for Atlassian integrations only).
Source port: 80. 80 is used for users that access GoRetro 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 on Google Cloud and use GCP Security Policies).
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.