← sources

Chrome Nearby Devices Permission - PSA

source: reddit (reddit:homelab)published 2026-11-13 12:25ingested 2026-11-14 02:40

retained text

I'm deploying services on a local docker host to do some testing in my homelab.  Everything seemed to be working great.  A bit later in the evening I was on my mobile and started trying to reach all the services I just deployed and chrome is throwing "too many retires" and "too many redirects".  

Took a bit of time, but finally went down the rabbit hole deep enough to figure out that it was all caused by chrome not having the "Nearby Devices" permission granted.  

Android 17 now blocks connections to a whole bunch of network ranges if that permission isn't granted for apps

* [`10.0.0.0/8`](http://10.0.0.0/8) (RFC 1918 private space)
* [`172.16.0.0/12`](http://172.16.0.0/12) (RFC 1918 private space)
* [`192.168.0.0/16`](http://192.168.0.0/16) (RFC 1918 private space)
* [`169.254.0.0/16`](http://169.254.0.0/16) (Link-local / Auto-IP)
* [`100.64.0.0/10`](http://100.64.0.0/10) (Shared CGNAT space — also the range used by NetBird/Tailscale overlays)
* **Multicast & Broadcast** (including [`255.255.255.255`](http://255.255.255.255), mDNS, and SSDP discovery)

document fetched 2026-11-14 00:39 · canonical https://reddit.com/r/homelab/comments/1xv6j68/chrome_nearby_devices_permission_psa