13
submitted 2 weeks ago* (last edited 2 weeks ago) by Sunny@slrpnk.net to c/selfhosted@lemmy.world

Hi there good folks! Trying to wrap my head around how this stack works. Previously I've been using NextDNS for this and it worked wonders. However, I've wanted to explore other options and have now gone with the Adguard+Unbound route on a RPI 4B.. This setup defo works, its blocking what I want blocked, but its created a new issue I've not had before. On my Graphene OS phone, as long as this setup is "active" (e.g. over Tailscale), all my notifications through various applications are getting delayed. Each notification come roughly 10 min late, if at all, or appear as soon as I open the corresponding app. I'm pretty sure this caused by either Adguard or Unbound but betting my money on Unbound - as I don't see any relevant DNS queries being blocked.

I am still a little unsure of what is causing this issue so if anyone would be able to enlighten me on how I could troubleshoot this issue I would be very grateful.

top 2 comments
sorted by: hot top controversial new old
[-] alwayssitting@infosec.pub 4 points 2 weeks ago* (last edited 2 weeks ago)

Try changing to another upstream DNS server in Adguard (such as https://dns.cloudflare.com/dns-query) and see if the problem gets resolved?

[-] hendrik@palaver.p3x.de 4 points 2 weeks ago* (last edited 2 weeks ago)

Sounds like you're blocking the servers which are supposed to push the notifications to you?! I think that's called Google Cloud Messaging.

You'd need to figure out which blocklist you enabled that does this. And either disable it, or add an entry to your allowlist.

Or do away with GCM and set up your own push provider like ntfy and additionally use apps from F-Droid that support this different push provider.

Edit: https://github.com/AdguardTeam/AdguardForAndroid/issues/3486 and there are several other bugreports. Also make sure you've disabled battery optimization for the Unbound(?) app.

this post was submitted on 10 Nov 2024
13 points (84.2% liked)

Selfhosted

40406 readers
522 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS