Override access URL for Channels DVR

Channels DVR Server
#21

Thanks for the response. My understanding is Remote Streaming is using a DDNS basically with a Channels-supplied custom domain (plus some token-based OAuth). There must be very little effort to publish a static user-supplied custom DNS name in place of that Channels external service-side dynamic host instead, no? It would literally be one more text field config in the Channels DVR Server config that would just override your custom server-side logic.

Edit: This would essentially be a “Custom DDNS for Remote Streaming” field. Simpler than Tailscale support surely

#22

Yeah, my goal here is to avoid Channels being directly exposed to the Internet to improve my home network security posture. Yes it's written in Go and yes that provides some fundamental security benefits. That said, it seems like a reasonable ask but there seems to be no interest in exploring it. I don't want to have to use Tailscale or a VPN because I don't have a VPN client on a TV in another home where I run the Channels client app.

1 Like
#23

They basically don’t want to remove the authentication requirement when connecting to CDVR from any IP other than a local one.

The other way around that is not to use cloudflared but instead to use the cloudflare one client and a full warp connector which basically creates you a mesh VPN between sites and devices.

That’s how I do a lot as well as cloudflared for basic web apps I want to publish.

There’s a distinct difference between cloudflared tunnels and warp tunnels. I agree forcing people into tailscale isn’t really a solution when there’s many other options. All cloudflared tunnels are is a reverse proxy and any reverse proxy forces the authentication with this app which the devs don’t want to change.

#24

They don’t want to change how it works. It’s pretty simple.

1 Like
#25

In my case I still want authentication. I just need the ability to specify a different remote access URL which presumably would need to be stored in the Channels remote access mapping backend. It seems pretty trivial given everything is over HTTP; this just seems to be a feature request the Channels developers are unwilling to implement.