Fixing "server misbehaving" error in Miniflux

I've been self-hosting Miniflux on my Synology NAS (DS224+) using Docker Compose/Container Manager. My home network is powered by a GL.iNet Flint 2 router, which is running AdGuard Home for DNS-level ad and tracker blocking. All DNS traffic in the network flows through AdGuard.

After setting up Miniflux, I started encountering "127.0.0.11:53: server misbehaving" errors when fetching some RSS feeds. Little by little, some individual feeds would start to show this error. Refreshing any affected feed manually in Miniflux temporarily resolved the issue, but eventually, the issue would reappear.

I looked through GitHub issues and searched online for a solution. Eventually, I stumbled across a discussion where someone experienced similar problems, which turned out to be related to AdGuard Home. In their case, the issue was resolved by adding their specified docker network as allowed client in Adguard. Their situation was a little different from mine, but it led me to investigate further into AdGuard settings.

That’s when I found the setting called "Rate limit" in AdGuard Home. By default, it's set to 20 requests per second per client. Given that I have around 120 RSS feeds in Miniflux, it’s easy to imagine how a full feed refresh could quickly exceed that limit, causing some requests to fail.

I changed the "Rate limit" value to 0 — effectively disabling the limit.

Since making that change, I haven't encountered any more problems with Miniflux. Everything’s been running smoothly.

If you’re self-hosting Miniflux (or any service that makes frequent outbound DNS requests) behind AdGuard Home, and you're seeing intermittent errors, check your rate limits.