v1.4.6 — say why the connection failed
A small release with one purpose: when connecting a FreshRSS server fails, the screen now tells you why.
🐛 Fixes
- A FreshRSS on a private address now says so. Self-hosted instances usually sit on a LAN or a Docker network, and the proxy refuses private targets by default — the screen only said "failed to connect". It now names the block and the variable that lifts it,
PROXY_INTERNAL_HOSTS. (#8) - A refused API password is reported as a refusal, not an outage. FreshRSS answers the same way whether the API password is wrong or was never set, so the message covers both — and points out that this password is separate from your account password.
- Everything else stays generic, deliberately. An unreachable host, a dropped connection or an expired FriRSS session are never blamed on your credentials: only a cause the backend actually verified gets named.
📖 Documentation
- The install guide now covers the private-address case where you actually meet it, with the line to add and the log signature to look for.
- The Unraid Community Applications template gained the field.
PROXY_INTERNAL_HOSTSis offered up front instead of missing entirely, which is why it went unnoticed.
Existing containers keep their own copy of the Unraid template, so add the variable by hand there — a template update only reaches new installs.
Full detail in the CHANGELOG. Image: ghcr.io/fripix/frirss:1.4.6.