Nginx Proxy Manager fixed, and NPMplus support
The NPM source works again on current Nginx Proxy Manager
Nginx Proxy Manager 2.12 and later report a proxy host's enabled flag as true/false instead of 1/0. Homedex expected a number, so a scan of any current NPM failed to read its proxy hosts. It now reads both forms. If your NPM source showed an error, it needs no change: the next scan picks your routes up.
NPMplus
The same source now reads NPMplus (thanks @Selim042 for #14). NPMplus returns its session as a cookie instead of a token, and Homedex tells the two apart from the login answer, so there is nothing to choose.
- Give Homedex its own NPMplus account with view access to Proxy Hosts and Certificates, and without two-factor authentication (Homedex cannot type a code on every scan; it says so if you try).
- The NPMplus admin port uses a self-signed certificate unless
DEFAULT_CERT_IDnames a trusted one. Set it, or point the source at a proxy host with a trusted certificate that forwards to the admin port. Pinning a self-signed certificate is planned. - Disabled NPMplus locations are skipped, and hosts that serve files or nothing are listed without an upstream.
Other fixes
- Test connection on an NPM source always logs in, so a changed password is tested rather than answered from a cached session.
- Clearer messages for a wrong password, repeated failed logins (NPMplus rate-limits them) and missing view permissions.
Upgrading
No migrations. docker compose pull then docker compose up -d. The one-file install follows the 0.2 line, so it picks this up on its own.
Container images are published to ghcr.io/harshshah0203/homedex.