Remote access via my.channelsdvr.net not working

Channels DVR Server
#1

I am getting the following error in the browser when I go to my.channelsdvr.net:

{"error":"unauthorized access from XXX.XXX.XXX.XXX"}

Also, remote clients which were previously talking to the DVR won't playback, they say 'Playback failed'.

I can, however connect directly to the public IP of the DVR on port 8089. It had me click a link to generate a code, then paste that code into a field on the page and it let me in.

I reinstalled the app on one of the affected clients and it found the DVR again, but I'm hoping that's not normal behavior since I don't want to have to reinstall the apps on the clients often (DVR has only been up for 4 days).

I've tried turning off and on remote access per previous posts about this but that had no affect. It looks like in February 2020 this was an issue that was fixed with an update.

#2

Did some more messing around with it, and on the web browser trying to access the DVR remotely, I cleared cookies and was able to access it at my.channelsdvr.net.

Clients are still not able to play back, even if I try to re-login on the settings screen (new access code). Only fix for them I have found is to clear the app data and sign back in.

#3

Are you at home or trying to access away from home?

What kind of router are you using?

1 Like
#4

DVR is at an offsite location behind a Verizon FIOS router. I have ports manually forwarded (and set to manual in the DVR settings) but UPNP is also enabled on the router (and I can't disable it for other devices which need it on the network).

Clients are Amazon Fire TV 4k's behind a Peplink router connecting remotely to the DVR.

1 Like
#5

I think I figured this out. When I added the shortcut on my local client's browser to the remote channels DVR server, I just bookmarked the autogenerated subdomain XXXXXXXXX.u.channelsdvr.net That is the one that I got the failed access errors on, and went through the activation code process.

I can't remember if I tried the nonworking FireTV clients that I had to reactivate first, but if they were after my initial troubleshooting attempts of turning remote access off and on again and doing the activation code, maybe that is why the clients lost authentication with it.

Now I am using my.channelsdvr.net as the address to access the remote server and have not had any issues yet. Even though that redirects to the randomly generated URL for the server, is it better to use that?

#6

Yes.