DS918+: Unable to login to DVR

Channels DVR Server
#1

This was after disabling UPnP, my router is R7800. The automatic mapping did not work prior to me disabling it and I did manually map the port. Any thoughts?

2018/08/20 20:38:29 [SYS] Starting Channels DVR v2018.08.02.1754 (linux-x86_64) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2018/08/20 20:38:30 [HDR] Found 1 devices
2018/08/20 20:38:31 [SYS] Started HTTP Server
2018/08/20 20:38:34 [DVR] Recording engine started in /volume1/Plex/DVR
2018/08/20 20:38:34 [SYS] Bonjour service running for dvr-ds.local. [192.168.1.8]
2018/08/20 20:38:35 [SYS] Created database snapshot: backup-20180820.203834
2018/08/20 20:38:46 [IDX] Pruned 638 expired airings from USA-NY31534-X in 1.464205968s.
2018/08/20 20:43:39 [NAT] Failed to discover upnp: write udp4 0.0.0.0:51028->239.255.255.250:1900: i/o timeout
2018/08/20 20:43:39 [NAT] Failed to discover router using natpmp and upnp.
2018/08/20 20:50:10 [ERR] zeroconf: failed to handle query v4: dns: failed to unpack truncated message

#2

Are you trying to use the DVR at home or remotely? The login feature is only for remote access.

What client device are you using?

#3

I am trying both at home and at work. Using an iPhone X. Surprisingly both my iPad and Apple TV can do remote DVR, but iPhone has not been able to connect.

Same thing happens on MacBook Pro when I go: my.channelsdvr.net. (page does not load). Something going on with DNS. I can get to page via IP:8089.

#4

I tried reinstalling the application without success from accessing the DVR from my mac. Any thoughts on things I can do to get it working?

#5

You appear to be using some sort of VPN on your Mac? When the DVR tries to connect to the internet, it’s going through your VPN so the remote access DDNS is not being set correctly.

#6

I have a VPN setup on my Synology, let block the port from going to VPN and see if that helps. Thanks for that feedback. Will keep you posted.

#7

The issue is not the incoming port, but rather the outgoing connection from the DVR software to our servers. We use the source IP to setup your DDNS (so the app knows where your home server is).

#8

Understood, I’m trying to force the connection to go via bond1 as opposed to VPN. Are you using port 8089 to reach your your servers? I don’t have a proper router, so I’m trying to figure out how to make this work on the Synology box. Thank you for your help, this is great.

#9

Sorry, not sure why I kept saying Mac earlier. You’re on a NAS.

The outgoing port is 443 (for https). The server is community.getchannels.com if you’re able to filter by hostname. Not really sure what kind of VPN options are available on Synology.

#10

Here’s what I got now by disabling the VPN:

2018/08/22 21:03:26 [SYS] Starting Channels DVR v2018.08.02.1754 (linux-x86_64) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2018/08/22 21:03:26 [HDR] Found 1 devices
2018/08/22 21:03:27 [SYS] Started HTTP Server
2018/08/22 21:03:29 [DVR] Recording engine started in /volume1/Plex/DVR
2018/08/22 21:03:29 [SYS] Bonjour service running for dvr-ds.local. [192.168.1.8]
2018/08/22 21:03:29 [NAT] Failed to discover upnp: No WANDevice found in http://192.168.1.2:1400/xml/device_description.xml
2018/08/22 21:03:29 [NAT] Failed to discover router using natpmp and upnp.
2018/08/22 21:03:29 [SYS] Created database snapshot: backup-20180822.210329
2018/08/22 21:03:31 [ERR] zeroconf: failed to handle query v4: dns: failed to unpack truncated message
2018/08/22 21:03:39 [IDX] Pruned 2 expired airings from USA-NY31534-X in 319.913203ms.
2018/08/22 21:04:03 [ERR] zeroconf: failed to handle query v4: dns: failed to unpack truncated message

This is trying to use UPnP from my switch but not my router. I have my default gateway (router) configured for UPnP, not the switch. Let me see what the switch says.

#11

This is the XML file channels is looking at, not sure if this helps. Any idea why it’s not looking at my default gateway for this request?

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>1</minor>
</specVersion>
<device>
<deviceType>
urn:schemas-upnp-org:device:InternetGatewayDevice:1
</deviceType>
<friendlyName>GS908E-1 (B0:39:56:97:_removed_)</friendlyName>
<manufacturer>NETGEAR</manufacturer>
<manufacturerURL>http://www.netgear.com</manufacturerURL>
<modelDescription>
GS908E 8-Port Gigabit Ethernet Web Managed Lifestyle Switches
</modelDescription>
<modelName>GS908E</modelName>
<modelNumber>v1.0.0.3</modelNumber>
<modelURL>http://www.netgear.com</modelURL>
<serialNumber>_removed></serialNumber>
<UDN>uuid:63a06c36-79fa-61f7-139c-33fc66b663f6</UDN>
<presentationURL>http://192.168.1.2</presentationURL>
</device>
</root>
#12

That is not related to the DNS issue. UPNP is only used to try to open the port.