# Installing Screenly OSE with balenaCloud

**URL:** <https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430>\
**Category:** Anthias\
**Created:** [December 4, 2020, 9:10am UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430 "2020-12-04T09:10:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![viradhanu](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/viradhanu/32/226_2.png) [@viradhanu](https://forums.screenly.io/u/viradhanu)\
**Post date:** [December 4, 2020, 9:10am UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430/1 "2020-12-04T09:10:51Z")

</div>

Hi,  
I tried to install Screenly with balena using the latest repo (master branch). It built just fine.  
Here in balena, I used “production” as the device variant type (OS variant). I can access the Screenly dashboard using public device url. But if I add some assets and activate them, it does not appear in the screen.

I notice that I’m getting error such as

> DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, …

I tried all the solutions mentioned in the below link, but no use.  
[How to turn off ‘protected-mode’ in Redis?](https://serverfault.com/questions/861519/how-to-turn-off-protected-mode-in-redis#:~:text=1)%20Just%20disable%20protected%20mode,to%20make%20this%20change%20permanent.)

Can you guys suggest me some tips to get rid of this issue?

---

<div class="post-metadata">

**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\
**Post date:** [December 9, 2020, 3:54pm UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430/2 "2020-12-09T15:54:42Z")

</div>

This sounds like something that has been fixed recently. Pull down the latest changes to the master branch and redeploy to Balena.

---

<div class="post-metadata">

**Author:** ![greysquirrel](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@greysquirrel](https://forums.screenly.io/u/greysquirrel)\
**Post date:** [December 9, 2020, 11:30pm UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430/3 "2020-12-09T23:30:16Z")

</div>

I have exactly the same problem. I did the build recently and used the screenly-ose-master zip downloaded from gitHub on 3/12/2020. How can I check if there has been an update?

I will repeat the process when I get time but in the meantime if anyone has fixed this issue I’d like to know

Thanks

---

<div class="post-metadata">

**Author:** ![greysquirrel](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@greysquirrel](https://forums.screenly.io/u/greysquirrel)\
**Post date:** [December 11, 2020, 9:30pm UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430/4 "2020-12-11T21:30:05Z")

</div>

I downloaded and deployed the “master” version yesterday evening and it’s now working fine. I have also noticed that Screenly does not display when connected via an HDMI - VGA convertor but it works fine when plugged directly into my TV. I assume this is because my cheap HDMI to VGA convertor can’t cope with the resolution set by Screenly

---

<div class="post-metadata">

**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\
**Post date:** [December 29, 2020, 9:56am UTC](https://forums.screenly.io/t/installing-screenly-ose-with-balenacloud/430/5 "2020-12-29T09:56:17Z")

</div>

Yeah this is most likely due to the HDMI handshake not working. You might be able to work around that by setting `hdmi_force_hotplug=1`. You might also need to some of the other settings.