Clarification on How to Push Code from GitHub Repo

Running on a RPi 3B+. On restart I run dmesg and get this output.

There seem to be some errors here.

Tried on Chrome, Firefox and Edge with same results.

Tested camera module on another Pi 3B+ and it worked fine.

Specific errors at:

[    0.844659] Warning: unable to open an initial console

[    1.201988] udevd[287]: Specified group 'render' unknown
[    1.202492] udevd[287]: Specified group 'kvm' unknown

[   11.217655] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1

[   11.452775] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   11.463229] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: May  2 2019 02:39:18 version (r714225 CY) FWID 01-e539531f

Those are nothing to worry about. Can you share the uuid for the device and enable support access for it so we can look a little closer please?


You also need to Grant support access from the Actions side panel in the device dashboard page

Just granted access for 1 day.

Just extended it after realizing it was the weekend.

I’ve just checked the device and it does provide the video feed.

When you change the env variable, the supervisor restarts your app services on the device. Do you think you could try getting the feed before the service was ready after such a restart?

I’m not sure what you are asking me to do. Could you clarify the steps for doing that?

the application gets restarted when you update environment variables. This takes some time during which the application is down. The question Is whether it possible that you were trying to access it right after updating the environment variable when the application was still restarting?
Looking at the device right now it looks that the video feed works correctly.

I have been able to test it out on some different devices with mixed results:

Windows 10 - Build 19041
Does not work on any browser

Windows 10 - Build 15063
Works on Firefox only

Android Phone running Chrome browser - works

iPhone running Safari browser - works

I am wondering in the problem with my first PC might have something to do with the new Windows update.


I was just able to test the camera (Chrome on Ubuntu) at the external URL and it worked properly. If you’re using the LAN address ( it will be reachable only by devices on that subnet. Can you confirm you’re having issues with the public URL or just the LAN address?

I meant to add that the version of Windows shouldn’t matter – unless the new build has different security settings or something similar that need to be acknowledged. However, since the balenaCam project is accessible via port 80, permissions shouldn’t be necessary.


I’m using the public url in all cases.

Hello Steve, thank you for your message! It’s really strange that it’s not working on your Windows 10 (actually only it’s working on your Firefox).
Could you please check if your browsers have WebGL and other graphical requirements activated on the Firefox version that works?

WebGL seems to be enabled on both. There also does not seem to be much consistency on which devices work and which do not. The only device that consistently works is an Android phone running Chrome.

Hey @steve_cline

I’ve just tested the public URL from a Windows 10 machine (as well as an OSX one) and could access the feed perfectly. It’s probably some weird configuration issue in your PC. Can you capture the console logs in one of the non-working chrome devices and paste the result here?


Here you go:

Hey there Steve,
You seem to have pasted the logs from the device on balenaCloud.
The logs that would be helpful are the chrome browser logs when trying to view the feed. You can press Shift + CTRL + J to access it.

However, in my opinion this seems to be related to browsers hiding the local IP address from WebRTC. Can you try the steps listed here and see if it helps?

pasted here for your convenience:

Chrome browsers will hide the local IP address from WebRTC, making the page appear but no camera view. To resolve this try the following

  • Enter this URL in your browser: chrome://flags
  • Ensure the media flag is enabled (this will give you access to other features)
  • Now set “Anonymize local IPs exposed by WebRTC” to Disabled
  • Refresh your app page

Firefox may also hide local IP address from WebRTC, confirm following in ‘config:about’

  • media.peerconnection.enabled: true
  • false

That fixed it! Thanks!