androidul

assuming that you’re to expose that to the Internet, my recommendation is to deploy only

• WAF solution, such as github.com/corazawaf/coraza-caddy
• bot blocker such as anubis.techaro.lol/docs/admin/environments/caddy

complicate the setup too much and it’s going to rather be more painful to maintain and also much easier to misconfigure.

The WAF covers OWASP Top 10 so that should give you around 70% protection which is still better than nothing

hmm I wonder if it’s because of the recent subscription hike … hmmmm

I was pondering the same for last couple of days and had some thoughts on how to make it feasible. My research led me so far to 2 prerequisites:

1. must have Anubis in front
2. must have a WAF solution in place that covers at least OWASP Top 10

I found pretty good Caddy documentation that covers both, so I think I’ll deploy a secondary Caddy reverse proxy that’ll perform such ops for public facing services.

Of course, I currently have only 1 Caddy instance reverse proxying my internal services, haven’t reached the part on traffic handling when my devices are connected to the “safe network” (aka my home LAN)

• WAF
• Anubis

I started selfhosting just because throwing cash on subscriptions at big corpos is not feasible since subs are increasing on a year-on-year basis. To my mind, if I’m going to self-host to yet again pay sub prices defeats the sole purpose of selfhosting.

That money you can pocket and invest in your own hardware for spare parts, upgrades & the like