I’d guess that you have another DNS server on your network which is trying to get the list of root name servers (what the . means) via AdGuard.

I’d guess that there are so many queries because something is going wrong with it’s attempt to get the root name servers from AdGuard so it’s doing it over and over (because it can’t function without them).

Debian. Always Debian.

I understand why, I just wish there was a way to do notifications without a centralised, internet connected server.

One of the things I do is build communications systems for scientific crews who are often working in places with local wifi but no internet. They’d really like to have a Matrix server (or similar) they can use to send each other messages. But as far as I’ve been able to determime this is currently impossible. :-(

Deltachat is the best solution I’ve been able to find.

Sadly, I believe web push notifications still go through a centralised server provided by the browser developer.

You’re asking r/selfhosted where to not selfhost something.

I thought limits only worked in swarms?

I just checked the docs and didn’t see anything about ntfy accepting smtp? This would be useful, what am I missing?

You have climbed mountains and gained skills. Congratulations my friend, now bask in the soothing waters.

I managed OpenLDAP servers professionally for years. You don’t want to use OpenLDAP unless it’s something you want to learn about.

LLDAP (or GLAuth) does everything you need in a homelab context for a fraction of the effort, complexity, and hassle.

Assuming it’s a Linux server at home and you can use SSH on your work computer, there’s a couple ways to do this.

• Install a web based terminal client
• Setup Cloudflare tunnels on your home server and use the the SSH proxy. I do this with a simple helper in ~/.ssh/config:

Match host "*.cf"
  ProxyCommand /usr/local/bin/cloudflared access ssh --hostname $(echo %h | sed 's/\.cf$/.homelab.nz/')
  ForwardAgent yes

Thank you, didn’t realise that!

This works pretty well for Postgres.

https://github.com/ankane/pghero

The reputation problem with hosting email at home is that most residential IPs are blacklisted.

The way around this is to relay your mail through another server (all SMTP servers support this, it’s often called a “smarthost”). This can either be an SMTP server you setup on a VPS with a clean IP or a commercial SMTP relay like Amazon SES. Cloudflare tunnels are for inbound traffic and can’t help with this.

Delivering email to a home SMTP server doesn’t have any reputation challenges, you just need to expose port 25 on your SMTP server to the internet (or again proxy it somehow).

Reverse proxy, Cloudflare tunnels, Tailscale.

One thing that threw me in the beginning was that the docs didn’t show examples in context. As an example, if you look at the basicauth docs it shows:

basicauth /secret/* {
	Bob $2a$14$Zkx19XLiW6VYouLHR5NmfOFU0z2GTNmpkT/5qqR7hx4IjWJPDhjvG
}...
}

Where can I use this? Globally? In the top-level of the virtualhost definition? If I’m reverse proxying, do I put it inside the reverse_proxy stanza? I used Apache for years and the docs always stated what context directives could be used in, eg.

https://httpd.apache.org/docs/2.4/mod/core.html#acceptpathinfo

I used Apache for many years. It’s great! But Caddy is simpler, easier and lighter weight.

The enshitification begins …

Because this is r/selfhosted. :-)

Nice!

I used Apache’s webdav server for years for this kind of thing.

https://httpd.apache.org/docs/2.4/mod/mod_dav.html

Caddy also has webdav support:

https://caddyserver.com/docs/modules/http.handlers.webdav