mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-11-19 14:40:27 +00:00
A name that only resolves through /etc/hosts or a resolv.conf search domain (resolver_mismatch) works for a static upstream only. nginx resolves a proxy_pass with a variable per request through its own resolver, which reads neither: the main target of every proxy host (proxy_pass $server) and a custom location in dynamic mode fail at request time. The health monitor and the config test still counted such a target as ok, so the host showed healthy. The probe is unchanged (POST /upstreams/check still answers ok with code resolver_mismatch). Only the interpretation is per target: forResolverTarget() marks a resolver_mismatch as not ok, with a message that says requests fail, for the main target and the locations saved (health monitor, from meta.nginx_locations) or rendered (config test, from the dry run's location states) in dynamic mode. Static locations and streams stay ok. The frontend shows resolver_mismatch as a yellow warning whether ok or not, and the host status lists it as "nginx can't resolve" instead of "not reachable". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 2fa.js | ||
| access-list.js | ||
| audit-log.js | ||
| certificate.js | ||
| dead-host.js | ||
| host-test.js | ||
| host.js | ||
| ip_ranges.js | ||
| log-viewer.js | ||
| nginx.js | ||
| proxy-host.js | ||
| redirection-host.js | ||
| remote-version.js | ||
| report.js | ||
| setting.js | ||
| stream.js | ||
| token.js | ||
| upstream.js | ||
| user.js | ||