then your only option is to change the working site to https in the browser bar and click through the security warning, then try checking the option again
When I click on the https in the channels browser it tries to open the site with https and fails.
Oh ok my server ip is 10.0.0.2 so trying that seems to be working,
It was picking up the IP from my PC I was using the browser from not the server.
Looking good got these channels.
6000 KGW
KGWDT (NBC)
6001 KATU
KATUDT (ABC)
6002 KPTV
FOXP (FOX)
6003 KOIN
KOINDT (CBS)
Oh d'oh okay that's a bug, its using the wrong IP. Will fix.
1 Like
Fixed in prerelease, please try and confirm:
Version 2022.01.20.0115
If you access your DVR web UI from a browser using insecure http: and check [X] Local Networks via TV Everywhere, you're not prompted by the browser to allow location service and it results in this misleading error message "Your browser failed to retrieve your geolocation: User denied geolocation prompt"
In Firefox?
Yes, I can try again with Edge.
Using Edge with http: gives this message
Try again over HTTPS. Your browser failed to retrieve your geolocation: Only secure origins are allowed (see: https://permanently-removed.invalid/Y0ZkNV).
And the link http://192.168.1.3:8089/auth/forcehttps is to my DVR server.
Clicking that link leads to https://192-168-1-3.############.u.channelsdvr.net:8089/admin/settings
I then have to check the box again [X] Local Networks via TV Everywhere
And then it works.
But now I'm wondering how it resolved that url when I have remote access disabled and no port forwarded?
Uploading fix to show https links in more browsers
Much better. Two links to choose, both leading to the same secure https: location.
Works on Firefox now.
Also working in Brave.
1 Like
Is the link correct (server IP) in the latest build?
Working for me.
1 Like
Inquiring minds want to know. Care to share?
It's not using remote access. It connects in your home to the IP, over SSL
It connects and works even when I change the url from https to http. Not a secure connection then.
It causes some concern when you think you're at channelsdvr.net, but you're not.
Using 192-168-x-x.channelsdvr.net is the same as typing 192.168.x.x in directly. It's a hostname that resolves to the IP, because SSL certificates are based on hostnames.
No one outside your network can access 192.168.x.x using either method.
1 Like
Yes, I knew all that.
Question was how it resolved to my local private intranet IP address.
I'm guessing your server verifies it's me at the user subdomain (############.u.channelsdvr.net) and with proper auth will respond with my local IP.
Just wondering why if my browser was redirected to 192.168.1.3 it doesn't display that in the url.
It's like if you went to https://my.bank.com but were really at https://iownzunow.fool but your browser didn't show that url, you might have reason to be concerned.
Our server is not involved at all. It's simple DNS. I don't know if you're asking me how dns resolution works?
It's like DYN DNS, we essentially created every combination of x-x-x-x as a DNS record and pointed it to x.x.x.x
1 Like
Got it. Thanks.