My device is running a development-image of BalenaOS.
I can see my webapp running when I navigate to http://<deviceuid>.local/
inside the browser.
Also when I SSH to the HostOS and check my running containers with balena ps
I see it has one container exposing like such 0.0.0.0:80->3000/tcp
.
However when I run the balena tunnel <full deviceuid> -p 80:8080
command it does not forward the port and I cannot reach the webapp via browser on 8080.
It just prompts that it’s ‘waiting for connection’.
Fetching application by name 6b35227b44c7d080a69158082d1587db (string)
[Debug] Application not found
[Debug] Fetching device by UUID 6b35227b44c7d080a69158082d1587db (string)
[Info] Opening a tunnel to 6b35227b44c7d080a69158082d1587db...
[Info] - tunnelling localhost:8080 to 6b35227b44c7d080a69158082d1587db:80
[Info] Waiting for connections...
And after a minute or so the following
127.0.0.1:60471 => 127.0.0.1:8080 ===> 10.240.0.4:80 :: connect ETIMEDOUT 34.90.19.201:3128
[Error] :0 => undefined:undefined ===> 10.240.0.4:80 :: connect ETIMEDOUT 34.90.19.201:3128
[Error] :0 => undefined:undefined ===> 10.240.0.4:80 :: connect ETIMEDOUT 34.90.19.201:3128
[Error] 127.0.0.1:60479 => 127.0.0.1:8080 ===> 10.240.0.4:80 :: connect ETIMEDOUT 34.90.19.201:3128
[Error] :0 => undefined:undefined ===> 10.240.0.4:80 :: connect ETIMEDOUT 34.90.19.201:3128
I tried it with other ports like 22222 to gain SSH access via the tunnel but no result.