nginx-proxy-manager/docs
Tom Winnerl ea4109965f fix(review): count a resolver-only main target as a warning, not healthy
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>
2026-11-14 09:03:56 +01:00
..
.vitepress docs: upstream discovery page 2026-11-14 09:03:56 +01:00
scripts Docs update, use package version instead of latest, refer to better mariadb image 2026-02-19 08:36:41 +10:00
src fix(review): count a resolver-only main target as a warning, not healthy 2026-11-14 09:03:56 +01:00
.gitignore Migrate from vuepress to vitepress for docs site 2024-05-10 23:00:27 +10:00
package.json Docs update, use package version instead of latest, refer to better mariadb image 2026-02-19 08:36:41 +10:00
yarn.lock Update dependencies 2026-11-09 11:55:20 +10:00