Replies: 1 comment 1 reply
|
That error text points to a proxy, not to the private network setting. When Miniflux talks to an HTTPS URL through a proxy, it first sends Your curl probably works because your shell doesn't have the same environment as the Miniflux service. Check what the process really sees: If If instead the proxy comes from Miniflux itself ( I reproduced it with 2.3.1 and 2.3.3 in Docker (squid proxy that can't reach docker.internal): same error on both, and NO_PROXY fixed it. So the upgrade alone won't change anything. Relevant code: request_builder.go. Do you have a proxy configured anywhere on that host? |
Uh oh!
There was an error while loading. Please reload this page.
I set up an internal system with FlareSolverr docker to workaround CDN.
But while it used to work, it does not anymore
but if I try in my browser or curl, it works fine
FETCHER_ALLOW_PRIVATE_NETWORKS=1 is set in /etc/miniflux.conf
miniflux 2.3.1. will upgrade to 2.3.3 soon
All reactions