Luckily grapheneos allows a hybrid approach so allows just the lan subnet permission without the wider nearby devices permission.

Haven't been brought to 17 yet thankfully.

My long term solution is to not use android. My short term solution will likely be to use android even less, and be even more pissed at Google.

Why are permissions so damn confusing? I say this as someone who knows why permissions are needed, such as location to find nearby devices. But why must we keep track of "permission X is for thing unrelated to X" in our heads? Now I haven't tried to make a permissions system for the masses, so I guess I can't say too much, but it doesn't seem that difficult to just make the permission name relate to what it does and provide a short synopsis for it.

Why not just grant the permission to the apps?

Relatedly, I think this is why Google Home and casting to Chromecast have stopped working reliably on my phone. Anyone figure those out? I've already tried granting permissions. Or it may be something GrapheneOS is doing.

Ran into this issue a few days ago, exactly the same way you described.

I am on GrapheneOS and figured it was something to do with a a setting where it's blocking network access for my specific browser app. After reading your post I see it's a android 17 feature.

Checked all the settings in my browsers related to DNS at first and was stumped for a bit, until I flipped on the nearby device setting and everything worked.

I also looked into the DNS settings under Network & Internet > Private DNS. Make sure your phone is using your local networks DNS server. Just make sure to understand the implications of changing this (especially when you disconnect from you're home networks DNS). Also making sure your home DNS is not defaulting to your ISP DNS.

Two websites that help me sanity check myself

• Dnscheck.tools
• dnsleaktest.com

I gave permission to Firefox, but honestly most of my services weren't affected because I connect to 99% of them via Tailscale which doesn't seem to trigger the permission. (Yes that was an absolute nightmare to figure out why only one service was failing to connect)

confused me when I suddenly had to give Firefox this permission to access websites on my LAN

More ways to control what can access what is a welcome change for me

(I'm on GrapheneOS but yeah, Android 17 based now)

Thanks for the heads up. This would have been a nasty surprise followed by unknown duration of hair pulling.

Oooh. I haven't updated it yet. Good to know as I will likely run into the same issue.

My phone is still on 14 so uuuhhh I'm fine I guess?

I had this issue in firefox. And only firefox. Was pulling my hair for hours. Wish I had been warned.

Anyway I just gave firefox the permission and the issue was resolved. Native apps seem unaffected. Which makes me think maybe this is an opt in setting right now?

Took me about an hour of reconfiguring everything in my network and still not having my phone load the damn page to finally try it on my desktop and it worked flawlessly, rebooted my phone and it finally gave me the pop up in the picture. So stupid.

Haven't noticed it yet because my services are on a different network than my clients

My solution is LineageOS as it functions on dozens if not a couple hundred phones. Rocking a One+ currently.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

[Thread #115 for this comm, first seen 27th Sep 2026, 20:10] [FAQ] [Full list] [Contact] [Source code]

It works but I wouldn't call it the cleanest solution, more a workaround. As far as I know only apps targeting SDK 37 are affected, older apps still get the permission implicitly. So the proper way would be to just grant "Nearby devices" to the apps that need it e.g. Immich or Jellyfin and if an app doesn't ask for it that's actually a bug and worth reporting, because it should request the permission as soon as the server resolves to a local IP. I also find the "Nearby Devices" title a bit misleading for apps that only need it to reach your own server, but on the other side it gives a somehow proper hint what the permission actually allows.

I had my DNS configured so my public-facing server resolved to a local IP address when on my LAN. This meant that my web, immich, xmpp, NTP, jellyfin and DoH servers all resolved to a local IP address on wifi.

I unfortunately don't have an answer to your question since I'm not on Android 17, but I do want to ask about this part. What's the benefit of this? Does it improve speed when streaming on Jellyfin?

Do you have any network segmentation is all your stuff on the same lan?

You also could try IPv6 public or private addresses

this is how they know who is even looking at stuff on their own network. holy shit