Hey guys, do you know why I can’t access services on .local addresses in Chrome on Android? It worked just fine until now.
I can access my server with no problem, but when I try to launch the UI of any service, it doesn’t work. There’s no problem on Windows or via Tor, so I assume the services are running fine.
I tried reinstalling the CA certificate and deleting the Chrome cache, but it’s still not working. 
Thanks for your help.
If it worked before, then the common reasons why it wouldn’t work don’t apply to you.
It could be as simple as you having jumped to another Wifi network without noticing (like if your router has a guest wifi network).
I have the same issue - I can access .local sites on MacOS, Linux, and iOS, but not on Android. It worked fine until recently?
I have also reinstalled CA Certificate with no effect.
Have you tried different browsers? You’ll need to test every variation of everything you can think of to narrow the issue down.
Yes - I have tried multiple browsers.
Here is one other clue: I can access the .local English readable addresses (alpha-beta.local/system for example) but cannot access any services with cryptic .local addresses (https://pw5n34uccu3ustyb7orkf3t7qxjdlygfysx7inktxvckivrzilqksvid.local for example)
Same here. I’m glad that I’m not alone with that, at least. 
It looks like something changed in android after some update, because my network setup didnt change for years and it worked with no problem.
And this is stock Android rather than GrapheneOS?
Could you both give me your versions?
I use Oneplus Nord 2T with Android 14 and their OxygenOS (security update is August 1. 2025)
I also tried it with an older Oneplus 5T with Android 10, and the result is the same. So my theory around android updates is kinda weak. 
Anyway, works just fine with Win 11 on the same network.
GrapheneOS release 2025090800
This does indeed seem to be a bug in Android/Chrome that affects Chrome-based browsers.
Firefox-based browsers appear to be unaffected.