Commands

Scenario/Error message	Likely meaning (TL;DR)	Recommended next steps
customer is experiencing some issues with tunneling. They have multiple other Atmosphere processors at this particular site they're not currently experiencing this issue with. They've attempted connection using multiple computers and private browsers.		If this is the only device experiencing the issue, while other devices of the same model on the same network are working as expected, it does narrow the likelihood that the root cause is specific to this device. Generally speaking, if there were an issue with our SSH tunneling service, we would expect to see a much broader impact across multiple devices and customers.
Tunneling returns a 502 Bad Gateway error	The tunnel was established, but the device did not return a valid response.	Verify that the device web server is reachable locally, make sure the forwarded port is correct, and confirm there is no HTTP/HTTPS mismatch or device-side firmware issue.Another possible cause is that the tunnel is established before the web server becomes available. Another possible issue is that the tunnel is created before the web server is active

Scenario/Error message

Likely meaning (TL;DR)

Recommended next steps

customer is experiencing some issues with tunneling. They have multiple other Atmosphere processors at this particular site they're not currently experiencing this issue with. They've attempted connection using multiple computers and private browsers.

If this is the only device experiencing the issue, while other devices of the same model on the same network are working as expected, it does narrow the likelihood that the root cause is specific to this device.

Generally speaking, if there were an issue with our SSH tunneling service, we would expect to see a much broader impact across multiple devices and customers.

Tunneling returns a 502 Bad Gateway error

The tunnel was established, but the device did not return a valid response.

Verify that the device web server is reachable locally, make sure the forwarded port is correct, and confirm there is no HTTP/HTTPS mismatch or device-side firmware issue.Another possible cause is that the tunnel is established before the web server becomes available.

Another possible issue is that the tunnel is created before the web server is active