Unable to install on Synology DS918

It says your Channels DVR package is running and listening on port 8089, so no idea why you can't access it via a web browser.

Have you looked at your Synology firewall settings to see if that may be blocking your access?

After you ssh in, run this command to see the last 10 lines of the Channels DVR log

tail /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log

too see more lines use the parameter -n # for # lines, example of 40 lines below

tail -n 40 /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log

You can substitute the command head instead of tail to see the first 10 lines of the log.

head /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log

and to see the first 40 lines

head -n 40 /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log
1 Like

alteric@BattleMedia:~$ tail /volume1/@appstore/ChannelsDVR/channels-dvr/data/channels-dvr.log
2020/07/25 18:55:57.033888 [SYS] Starting Channels DVR v2020.07.19.1752 (linux-x86_64 pid:24051) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2020/07/25 18:55:57.511919 [HDR] Found 0 devices
2020/07/25 18:55:57.512101 [ERR] Failed to refresh auth: missing oauth client
2020/07/25 18:55:57.513658 [SYS] Started HTTP Server
2020/07/25 18:55:57.515273 [SYS] Bonjour service running for dvr-battlemedia.local. [192.168.1.73 169.254.84.190]
2020/07/25 21:18:46.178882 [ERR] Failed to refresh auth: missing oauth client
2020/07/26 00:18:46.231421 [ERR] Failed to refresh auth: missing oauth client
2020/07/26 03:18:46.468736 [ERR] Failed to refresh auth: missing oauth client
2020/07/26 06:18:46.763885 [ERR] Failed to refresh auth: missing oauth client
2020/07/26 09:18:46.983174 [ERR] Failed to refresh auth: missing oauth client
alteric@BattleMedia:~$

what does this mean?

Looks normal, so it didn't crash, it's waiting for you to connect via a web browser and set it up.

Run this command and copy/paste the output here:

curl -v http://192.168.1.73:8089/status

alteric@BattleMedia:~$ curl -v http://192.168.1.73:8089/status

GET /status HTTP/1.1
Host: 192.168.1.73:8089
User-Agent: curl/7.54.0
Accept: /

< HTTP/1.1 200 OK
< Cache-Control: no-cache, no-store
< Content-Type: application/json; charset=utf-8
< Date: Sun, 26 Jul 2020 17:09:00 GMT
< Content-Length: 415
<
{"arch":"x86_64","description":"the daemon powering Channels DVR","features":{"bonjour":true,"comskip":true,"cpu":true,"dvr":false,"guide":false,"nat":false,"on_later":false,"remote":false,"roku":false,"transcode":true,"tve":false},"name":"channels-dvr","os":"linux","start_time":"2020-07-25T18:55:56.817132096-05:00","subscription":"","url":"https://getchannels.com/dvr","username":"","version":"2020.07.19.1752"}
alteric@BattleMedia:~$

Ok good now run the same command on your Mac

Last login: Sat Jul 25 17:19:07 on console

The default interactive shell is now zsh.

To update your account to use zsh, please run chsh -s /bin/zsh.

For more details, please visit https://support.apple.com/kb/HT208050.

Alterics-MacBook-Pro:~ al$ curl -v http://192.168.1.73:8089/status

  • Trying 192.168.1.73...

  • TCP_NODELAY set

  • Connection failed

  • connect to 192.168.1.73 port 8089 failed: Operation timed out

  • Failed to connect to 192.168.1.73 port 8089: Operation timed out

  • Closing connection 0

curl: (7) Failed to connect to 192.168.1.73 port 8089: Operation timed out

Alterics-MacBook-Pro:~ al$

@tmm1 This I can't understand.
Why would the browser be able to access the Synology admin page, but not the Channels DVR both at the same ip address?

Wondering if the Mac can ping the Synology and the Synology can ping the Mac?

alteric sounds like you have a vpn on your synology or it's network setup is misconfigured

try pinging your synology from your mac
ping 192.168.1.73

and your mac from your synolgy
sudo ping -c 4 192.168.1.?
where ? is the ip address of your mac

then ssh in to your synolgy and run
route -n

I had the VPN app installed, so uninstalled it. Still no luck. It pinged successfully. After ding the route -N command. I received these results.

alteric@BattleMedia:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 ovs_eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ovs_eth0
alteric@BattleMedia:~$

When did you last do a full reboot of your NAS? After making so many different configuration changes, it's common for some older settings to remain in the cache, routing tables, etc. (This is especially the case when changing network settings.)

It sounds juvenile, but when did you last start from zero—meaning, a full restart of each device between the one you are trying to access (your NAS in this case), and the computer you are using to access it (you Mac)? That includes a full hard restart of each piece of network equipment in between: switch, wireless AP, router, etc. Power off your NAS and Mac and reboot your network equipment. After your network equipment is fully up, restart your NAS. After that is fully up, start your Mac. (Troubleshooting like this is always easier when you can narrow everything down to the simplest scenario; rebooting ensures cruft from previous attempts won't affect future attempts.)

routing table looks fine assuming your router is at 192.168.1.254

I would keep the vpn disabled until you figure it out, I agree with racameron

I don't want to appear rude, but I literally just installed on a DS918+ and had no issues.

I'm using DSM 6.2.3-25426 Update 2 connecting through a Apple AirPort Extreme Time Capsule (Firmware 7.9.1 Custom 12TB) using a MacBook Pro (Mac OS 10.15.6) and Safari (13.1.2)

I did a manual install of the Channels Downloaded spk and clicked open. When I opened it went to the settings page for Channels DVR.

I just came here to post a feature request and noticed your issues. I hope it all works out.

I have basically the same setup. For some reason mine will not open. Good to know. That means I have something that I need to uninstall or something blocking. At least I know the firmware is fine. It is something on my end.

I added port forwarding manually in the AirPort for the DVR to be accessible outside of my local network... but that's it and that's after the initial setup.

just tried that. I have no idea what this could be? I am totally lost.

Actually, ping uses ICMP, separate and different from both UDP and TCP. Decent and proper packet filters can allow ICMP packets while blocking both UDP and TCP.

I stand corrected :blush:
Poor choice of words.
What I meant to say is a ping can get through a basic firewall even if UDP and/or TCP are blocked.

Still don't understand how he can access the Synology admin web UI at the same IP as the Channels DVR web UI, unless access to the Synology is being done through the Internet.

Have you tried different computers? Could be localized to the one you are trying to setup from.

Are you using an access point instead of a router?