You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
I have tried to get the Balena-cam working today on both a Pi 3A+ and a Pi Zero W via the "Deploy with Balena" route but while both connect to my account / the cloud, each one yields the following error when trying to access the public IP address to view the camera:
"We encountered an error when reaching this balena.io device:
(ID)
tunneling socket could not be established: 500
One possible reason is because nothing is listening on port 80 on the device."
I have tried the current builds (as of today, 03/07/22) for the Pi Zero and both 32 and 64 bit versions for the Pi 3. In all cases I am using the official camera module and the hardware in each case works from Pi OS.
The other devices I have currently running other Balena tasks are all still connecting so I don't think it's a connectivity issue my end or a service issue at Balena.
I have tried to get the Balena-cam working today on both a Pi 3A+ and a Pi Zero W via the "Deploy with Balena" route but while both connect to my account / the cloud, each one yields the following error when trying to access the public IP address to view the camera:
"We encountered an error when reaching this balena.io device:
(ID)
tunneling socket could not be established: 500
One possible reason is because nothing is listening on port 80 on the device."
I have tried the current builds (as of today, 03/07/22) for the Pi Zero and both 32 and 64 bit versions for the Pi 3. In all cases I am using the official camera module and the hardware in each case works from Pi OS.
The other devices I have currently running other Balena tasks are all still connecting so I don't think it's a connectivity issue my end or a service issue at Balena.
Here is the log from the Pis on startup:
Supervisor starting
Applying configuration change {"SUPERVISOR_POLL_INTERVAL":"900000","SUPERVISOR_DELTA":"1","SUPERVISOR_DELTA_REQUEST_TIMEOUT":"59000","SUPERVISOR_DELTA_VERSION":"3"}
Applying boot config: {"gpu_mem_1024":"448","gpu_mem_256":"192","gpu_mem_512":"256","start_x":"1","avoid_warnings":"1","disable_splash":"1","dtparam":["i2c_arm=on","spi=on","audio=on"],"gpu_mem":"16"}
Applied boot config: {"gpu_mem_1024":"448","gpu_mem_256":"192","gpu_mem_512":"256","start_x":"1","avoid_warnings":"1","disable_splash":"1","dtparam":["i2c_arm=on","spi=on","audio=on"],"gpu_mem":"16"}
Applying boot config: {}
Applied configuration change {"SUPERVISOR_POLL_INTERVAL":"900000","SUPERVISOR_DELTA":"1","SUPERVISOR_DELTA_REQUEST_TIMEOUT":"59000","SUPERVISOR_DELTA_VERSION":"3"}
Applied boot config: {}
Applying configuration change {"SUPERVISOR_VPN_CONTROL":"true"}
Applied configuration change {"SUPERVISOR_VPN_CONTROL":"true"}
Rebooting
Supervisor starting
Creating network 'default'
Supervisor starting
Can someone please offer me some assistance in this ?
The text was updated successfully, but these errors were encountered: