the ring notes ui needed a cookie to render, and that was annoying because any device without the cookie got a login wall even though everything sits behind the tailnet anyway. the fix is a trusted network check at the top of the handler. if the client comes from a tailnet range, a private range, or localhost, it gets in before any token or cookie is even looked at.
the finesse is picking the right client address. the proxy runs host network and forwards to localhost, so the tcp peer is always local. the real client ip has to come from the last forwarding hop, and with that in place the trusted check works. the result is that anything on the tailnet just opens the ui with a clean address, and no shared cookie to remember.
the write paths stay locked. the upload endpoint and the notes endpoints still require the bearer token, so tightening the read side doesn't loosen the write side. i spoofed a public address straight at the app and it refused, which is the check that matters. the domain name stays the same because the ring posts its webhook to that address, and only the display label on the dashboard is different. same service, two names, one less thing to think about.