S-B03 · portal nginx resolver hardcodes Docker DNS → 502 on podman #96

New Issue

not · 2026-07-16T13:43:37Z

not commented

2026-07-16 13:43:37 +00:00

The portal reverse proxies (apps/*/nginx.conf) hardcode Docker's embedded DNS (resolver 127.0.0.11) for their variable proxy_pass to the BFF. On rootless podman the per-network DNS is different (aardvark, e.g. 10.89.0.1), so every proxied call (/self-service/, /openbaar/register, /behandel/werkbak, decide, withdraw) returns 502 Bad Gateway — the portals load and login works, but no in-app data flows. Fine on Docker/Docker Desktop/CI.

The portal reverse proxies (`apps/*/nginx.conf`) hardcode Docker's embedded DNS (`resolver 127.0.0.11`) for their variable `proxy_pass` to the BFF. On rootless **podman** the per-network DNS is different (aardvark, e.g. `10.89.0.1`), so every proxied call (`/self-service/`, `/openbaar/register`, `/behandel/werkbak`, decide, withdraw) returns **502 Bad Gateway** — the portals load and login works, but no in-app data flows. Fine on Docker/Docker Desktop/CI.

not referenced a pull request that will close this issue

2026-07-16 13:43:37 +00:00

fix(infra): engine-portable portal nginx resolver (closes #96) #97

not added the type:bug area:infra labels 2026-07-16 13:43:39 +00:00

not closed this issue

2026-07-16 14:23:41 +00:00

not referenced this issue from a commit

2026-07-16 14:23:43 +00:00

fix(infra): engine-portable portal nginx resolver (closes #96) (#97)

Sign in to join this conversation.