Sigh. Why doesn't Miniflux like nginx. I used their suggested nginx config even.
Randomly 502s. Sigh. I guess I am going to learn....
Already am, to be fair. I have debug logs on for Miniflux and it is logging zero errors, and thinks it has responded just fine.

Miniflux says: May 10 08:30:34 rss miniflux[13383]: level=DEBUG msg="Incoming request" client_ip=192.168.1.190 request.method= GET request.uri=/history request.protocol=HTTP/1.0 request.execution_time=23.200117ms

And Nginx says: 2026/05/10 08:30:34 [error] 33626#33626: *1979 recv() failed (104: Connection reset by peer) while reading resp onse header from upstream, client: 192.168.1.1, server: example.tld, request: "GET /history HTTP/1.1", upstream: "http://192.168.1.198:8080/history", host: "example.tld"

webserver(nginx) lxc is on x.x.x.190 and Miniflux is on x.x.x.198 here, domain changed to protect the guilty. I keep piling stuff on the webserver container so thought I'd keep this separate. Hmm. Wondering if I should not have. It is random too, the response times Miniflux displays can be longer and it actually works fine. Then boom a bunch just don't.

Going straight to the IP:port it doesnt miss a beat ever, so this must be something to do with Nginx proxy_pass settings, surely. 🤔

#rss #selfhosting #whydoIdothistomyself #Miniflux #nginx

#WTF https://github.com/electh/nextflux/commit/1367f45330981c01578b309ab9521d2ba66ae395

#NextFlux #MiniFlux #RSS #NoAI