Here you go 
2017/06/30 20:29:53 [SYS] Starting Channels DVR v2017.06.29.2332 (linux-armv7l) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2017/06/30 20:29:53 [HDR] Found 0 devices
2017/06/30 20:29:53 [SYS] Started HTTP Server
2017/06/30 20:29:54 [SYS] Bonjour service running for xxx. [192.168.2.45]
Did you still need/want the other information you asked for earlier?
ps aux | grep channels
root 18794 0.0 2.6 853128 6464 ? Sl Jun30 0:10 ā¦/latest/channels-dvr
admin 29765 0.0 0.3 4636 932 pts/2 S+ 08:43 0:00 grep --color=auto channels
ls -alh /volume1/@appstore/ChannelsDVR/channels-dvr/data/
total 36K
drwxr-xr-x 2 root root 4.0K Jun 30 20:29 .
drwxr-xr-x 4 root root 4.0K Jun 30 20:29 ā¦
-rw-rār-- 1 root root 311 Jun 30 20:29 channels-dvr.log
-rw------- 1 root root 32K Jun 30 20:29 settings.db
Okay so the DVR is definitely running, and should be accessible via http://192.168.2.45:8089
Sounds like thereās a firewall or something thatās preventing you from accessing it, and also preventing the DVR from discovering your hdhomeruns.
I would check the network settings of your Synology and poke around your router settings.
What kind of router are you using? What is the IP of your hdhomerun?
So I have to preface things by saying again that I have a very limited, enough-to-get-by-but-learning-as-I-go sort of knowledge when it comes to all things network relatedā¦
My router is an Edgerouter X from Ubiquiti. If there are firewall settings I need to tweak - and it sounds like I need to do so - I would need to look into how exactly I need to do that (been meaning to do so anyway, so this is good reason to do so now ). Just donāt know where to startā¦
I donāt know if this means anything towards getting this cleared up, but I have ATT Uverse and used their gateway as my router initially, but when I upgraded my home network with a Ubiquiti WAP and the Edgerouter X, I configured the gateway to stop behaving like a router. Like i said, not sure if this impacts anything, but just full disclosure
My HDHomerun is at 192.168.2.72. The Channels app on my AppleTV sees it because it works perfectly fineā¦
Sorryā¦ I think I am creating more of a headache than anythingā¦
I fixed itā¦ Dumb me at some point enabled the firewall settings on my Synology NAS, so, I disabled it and it worked.
Ughā¦ I am dumb. Sorry for the drama; but I appreciate the help trying to get things all figured outā¦
It could have come on by default, Iāve had mine so long I canāt really remember but I turned it off if it did come turned on.
Second time this "blank 8089 screen" has happened to me. My set up is Synology NAS and Synology SRM (router). Check to ensure both my firewall on my NAS was DISABLED and port 8089 is open via uPNP. Last time this happened, I rebooted my NAS (not my router) and everything was back to normal. So off to chrome inspector, bundle.js:1 Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING off to https://stackoverflow.com/questions/23217824/neterr-incomplete-chunked-encoding. Removed the cookie/cached data in both my chrome browser as well as Safari, both are not loading the page. Thoughts on how to figure out what is going on?
