Remote DVR loads page header but no content

It's set to ON & Manual. Port 8089 is port forwarded in my router to the fixed IP address of the Linux Mint 20.3 computer running Channels-DVR. Port Checker shows the port open. If I go to http://my.channelsdvr.net from the settings page or my external IP:8089, both show the normal page header but nothing else loads with the browser's rotating circle going indefinitely. Other apps using port forwarding work fine. And of course local access works fine. Any suggestions appreciated.

For clarification are you on your home network when trying to go to mychannels. I have seen what you are describing with header only when you try to use mychannels on home network when the router does not support hairpin nat. In this case you need to use the server.ip:8089. If you are not on your home network mychannels should work.

Thanks for the reply. Yes, I'm trying from my home network where the server resides. As far as I know my router does not support hairpin nat. I have asked a friend to try my.channelsdvr.net and my external-ip:8089. We'll see. Thanks!

You can also use your phone and disable WiFi and test with cellular data in a browser. It should work with my.channels if your port forwarding is setup correctly. You can also test the phone app with the cellular data connection while you’re at it to make sure remote is working properly.

1 Like

I did turn off wifi on my phone and try both my.channelsdvr.net and my-ip:8089. I couldn't get past a login screen in one case and a request for an authorization code in the other. But I did try the channels app on the phone, as you suggested, and that worked! So I'm hopeful that my friend will be successful. I'm waiting to hear from her. In any case I think you solved it, and I'm very grateful.
THANKS!

The first time you go to my.channelsdvr from outside the local network you have to login with your channels credentials. After that it will remember. If you failed during this login you probably had a typo

My friend successfully accessed my server. Thanks again for solving this for me.