Hello! Could you please help me? I have this error:
Error: " Request error: tunneling socket could not be established, statusCode=500" when trying to reboot or restart container.
diagnostics tab : Some networking issues detected:
test_dockerhub: Could not query Docker Hub
test_balena_registry: Could not communicate with for authentication
Hello Anton, Im sorry I am not sure I understand what you mean about the public url, did you see that error when trying to reach the device publics URL? One thing which would help us understand what is happening is navigating to the diagnostic page and downloading the diagnostic report for the device. That should contain logs for the supervisor and other services which can help us debug these kind of issues
I am having the same error. I am using the balena cloud and motioneye to get this working but when I click on public device url and then the url it generates, I get this error.
How to fix that? Below is the message I get.
Error accessing device
We encountered an error when reaching this balena.io device:
UUID 7e3ca05ece739bcb2d0xxxxxxxxxxxxxxx
tunneling socket could not be established: 500
One possible reason is because nothing is listening on port 80 on the device.
I used the instructions as mentioned by bkjaya1952 above.
I am using pizerow instead of pi3.
I used the motioneye and pulled from docker per the instructions.
I get this error when I run it using the device public url.
Hi Friend
I didnβt try for pi zero . When creating an application and device , select the correct balena image compatible with pi zero. I have downloaded the balena image compatible with raspberry pi 3 .If the correct image canβt open the public device url , It is better to seek the assistance of balena team.To start the motionEye ,You will have to start motioneye container by running
balena start motioneye
or
Hi there, take a look at this thread for additional inspiration. the project it refers to is a little out of date, but it should give you a hint on how to make the software listen on port 80 so that device URLs will work automatically.
Alternatively, you can try this project, which is more up to date.