Skip to content

fix(e2e): wait for backend to be healthy before starting ssl-offloading nginx proxy (backport of #4551) - #4554

Merged
reinkrul merged 1 commit into
V5.4from
fix/4549-rfc021-nginx-depends-on-v5.4
Sep 18, 2026
Merged

reinkrul merged 1 commit into
V5.4from
fix/4549-rfc021-nginx-depends-on-v5.4

Conversation

@reinkrul

Copy link
Copy Markdown
Member

Backport of #4551 to V5.4.

V5.4 only has 2 of the 11 files master's fix touched: nuts-network/ssl-offloading/nginx and openid4vci/issuer-initiated. Of those, only ssl-offloading/nginx still has the affected nginx-fronts-nuts-node pattern — issuer-initiated on this branch predates the nginx proxy being introduced there, so it has no nginx service to fix. The other 9 suites don't exist yet on V5.4. Scope is narrowed accordingly; not a straight cherry-pick.

Assisted by AI

…ng nginx proxy

nginx resolves its upstream backend's hostname once, at config load
time, and never retries. With no depends_on, Docker Compose starts
the proxy and its backend concurrently, so if the backend's network
alias isn't registered yet, nginx crashes immediately with "host not
found in upstream" and stays down.

Backport of #4551 to V5.4. Only nuts-network/ssl-offloading/nginx is
affected: it's the only e2e suite on this branch with the
nginx-fronts-nuts-node pattern that master's fix also touched (the
other suites either don't exist yet on V5.4, or predate the nginx
proxy being introduced, as with openid4vci/issuer-initiated).

Assisted by AI
@reinkrul
reinkrul merged commit 717a931 into V5.4 Sep 18, 2026
8 checks passed
@reinkrul
reinkrul deleted the fix/4549-rfc021-nginx-depends-on-v5.4 branch September 18, 2026 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants