Channels on Synology. Updated from 1.0.5 to 1.1.0 on DSM 7 and now can't access

Channels DVR Server
#1

Just updated Channels DVR on my DS918+ Synology
I did a manual install without removing the older version
When done, I just had the new version which was running
Clicked open and got: Please visit this server via its local network IP to perform initial setup.

But I was on that IP and on same network. Waited longer and didn't work.

Uninstalled and reinstalled without change
Found one linked post here and checked permissions but I do not have a channels user created during install.

Appreciate any help

#2

What is the IP?

#3

internally it is the same as Synology - 192.168.1.40

#4

Tried both http and https just in case but no difference

#5

And just found I had to choose Advanced Permissions to find the channels user - enabled for /ChannelsDVR as well as /Data where I store most

Still no change when click Open on the program

#6

Copy paste the url in the browser bar when you see that error

#7

URL in Browser bar - http://192.168.1.40:8089/

Main body of page:

Please visit this server via its local network IP to perform initial setup.

#8

What is the IP of the local computer you're using to access? It sounds like there's a proxy or something else in between

#9

Wi-Fi is connected to Office and has the IP address 192.168.1.176

I ended up installing the Docker version on Synology and, besides having to manually input the IP for my HD HomeRun, I think I'm good. Only difference I can see is that I lost hardware transcoding as an option. Also, not to derail my own thread but there seems to be an issue with how Docker provides IP addresses in bridge mode that left me with a proxy situation in Remote DVR...

Still not sure why the native package won't let me in though (I stopped the Synology package when installing Docker and vice versa when trying to get into the native package; stopped Docker)

#10

You're going to kill me...

It was an Eero uPnP issue...again!

Don't know how/when but it was switched off

Turned it on and now can access. Eero is killing me

1 Like
#11

I would recommend sticking with the syno package if you're using TVE with Channels DVR.
(I was getting Chrome corrupted all the time in a container, but no issue with syno pkg)
To get hardware transcoding with the docker container, you need to add the device option to your docker run command.
--device /dev/dri:/dev/dri
Channels DVR Server - Docker

1 Like
#12

See the three posts starting with this one