this post was submitted on 27 Sep 2026
239 points (99.2% liked)

Selfhosted

62348 readers
1169 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

It took me a while to figure out why many of my self-hosted services were intermittently failing to connect on my phone after updating to Android 17. I eventually figured out there's a new ACCESS_LOCAL_NETWORK permission which means the "Nearby devices" permission is now required to access devices on the same network subnet. For an avid self-hoster, this can be quite a bit.

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. On Android 17, it all broke without warning. No error messages. No asking for extra permissions. Just silent packet dropping.

I've solved it by configuring my public-facing services to resolve to my external (static) IP address, even when inside the network. I couldn't make any internal services resolve to the external address (SMB, CUPS etc) because they are (obviously) not bound to my WAN interface.

I get why the change was made. A lot of apps were snooping around people's networks to gather intel. A potentially massive privacy violation.

Has anyone else had this issue? Is this the cleanest solution?

(page 2) 13 comments
sorted by: hot top controversial new old
[–] fleem@piefed.zeromedia.vip 3 points 1 day ago

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

[–] possiblylinux127@lemmy.zip 3 points 1 day ago (2 children)

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

You also could try IPv6 public or private addresses

load more comments (2 replies)
[–] unitedwithme@lemmy.today 4 points 1 day ago (1 children)

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

[–] Bazoogle@lemmy.world 2 points 23 hours ago

I am also a LineageOS user, though this feature seems like a good feature. You can block apps from being able to access your local network, which seems like a welcome restriction.

[–] Lenna@piefed.ca 2 points 1 day ago (18 children)

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?

[–] pHr34kY@lemmy.world 1 points 19 hours ago

Routing between two interfaces on the same NIC takes nanoseconds. You wouldn't notice a performance difference.

When I first set it up, I didn't have a static IP address, so it would not be great when it changed. I also want my server to remain reachable locally if my internet goes down. I had different firewall/ACL rules for wifi too. For example, some of my internal websites only prompt for a login if you're outside the network.

IPv6 has been awesome here. I have my server and clients on different /64 subnets in the same /48 block. The nearby devices on Android assumes only the same /64 is local.

load more comments (17 replies)
load more comments
view more: ‹ prev next ›