Devices unreachable

sheng · December 9, 2017, 1:49am

Saw that there was a brief outage earlier from status.resin.io. We’re able to access the dashboard, but our device public URLs (UUID.resindevice.io) are still unaccessible with the error message “tunneling socket could not be established: socket hang up”.

Anyone else having this problem?

pcarranzav · December 9, 2017, 8:29pm

Hi @sheng! Does the problem persist? It might have taken a while for things to get back to normal, e.g. for devices to reconnect to the VPN for the URL to work.

Topic		Replies	Views
Tunneling socket could not be established: socket hang up Product support	1	1292	February 13, 2019
Tunneling / Device Provisioning Issues Product support	8	860	May 30, 2017
Request error: tunneling socket Product support raspberrypi3	4	1961	February 18, 2019
Request error: tunneling socket could not be established, cause=socket hang up \| While services working properly Product support support , raspberrypi3	6	2624	June 9, 2019
my device randomly stopped working; is currently just showing balenacloud logo; Request error: tunneling socket could not be established, cause=socket hang up Product support	8	387	March 25, 2020

Devices unreachable

Related topics