My.channelsdvr.net redirect not working

Hey @maddox - I’m seeing something similar (not sure if related), but I have always used my.channelsdvr.net and it went right to admin page. Doesn’t seem to be working this morning.

Might be completely unrelated, just thought I’d mention.

We're looking into this.

I am also seeing this. There is an issue with the dynamic DNS service. You may want to update your system status page while you look into it.

Local connection to the server works fine. External network nmap and nc port forwards correctly to 8089, and shows it is active. When I use the check the external connection test in the General settings, it connects about 30% of the time, but mostly can't find the forwarded connection. When I go to the web via my.channelsdvr.net, it can't find it, but when I use the direct IP of my home network and not the dynamic DNS that the login gives me, I can connect without issue, and even stream video.

There is something amiss with the dynamic dns service:

e***@wasted ~ --> nslookup b[hidden].u.channelsdvr.net
;; connection timed out; no servers could be reached

e***@wasted ~ --> nslookup google.com
Server:		138.72.247.105
Address:	138.72.247.105#53
Non-authoritative answer:
Name:	google.com
Address: 172.217.12.110

e***@wasted ~ --> nslookup channelsdvr.net
Server:		138.72.247.105
Address:	138.72.247.105#53
Non-authoritative answer:
Name:	channelsdvr.net
Address: 104.26.11.141
Name:	channelsdvr.net
Address: 172.67.74.22
Name:	channelsdvr.net
Address: 104.26.10.141

e***@wasted ~ --> nc -vz b[hidden].u.channelsdvr.net 8089
nc: getaddrinfo: nodename nor servname provided, or not known

e***@wasted ~ --> nc -vz 99.88.[hidden] 8089
Connection to 99.88.[hidden] port 8089 [tcp/*] succeeded!
1 Like

@maddox @tmm1 @eric I am seeing the same thing (no remote access) on both of my servers.
09f170edeb9a.u.channelsdvr.net
5b4e1cdeaea5.u.channelsdvr.net

confirmed ports are opened.

See

This is down for everyone. There's no need to personally confirm it's happening to you.

We've identified an outage with a partner and we are monitoring their status.

We have routed around the issue and your dynamic dns hosts should be resolving again.