Skip to content

fix(learninggoalhub): pin nginx upstream to the unique server container name#9

Merged
florivn merged 2 commits into
mainfrom
fix/learninggoalhub-nginx-upstream
Jul 14, 2026
Merged

fix(learninggoalhub): pin nginx upstream to the unique server container name#9
florivn merged 2 commits into
mainfrom
fix/learninggoalhub-nginx-upstream

Conversation

@florivn

@florivn florivn commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

What changed and why

Staging has served 502 for all learninggoalhub API calls since examlense's server joined the shared hestia-edge network (#6): Compose registers the service name server as a DNS alias there, and our web container (also on hestia-edge) resolved its nginx upstream server to the examlense container instead of our own Spring server.

  • client/nginx.conf: proxy to learninggoalhub-server:8080 (unique container_name, only resolvable on our private network) instead of the generic service name.
  • infra/traefik/README.md: document the naming rule for services joining hestia-edge.

How it was tested

  • Root cause confirmed on hestia-test: docker exec from the web container showed server resolving to 192.168.2.5 (= examlense-server, connection refused) while learninggoalhub-server runs healthy at 192.168.1.3.
  • nginx -t passes with the updated config (nginx:alpine).

florivn added 2 commits July 14, 2026 13:15
…er name

The web container also sits on the shared hestia-edge network, where another
app's compose service named `server` registers the same generic DNS alias and
shadows our upstream — nginx then proxies /api to the wrong app's container
(502 on staging since examlense joined hestia-edge). Resolve the Spring server
by its unique container_name instead.
@florivn
florivn merged commit 3bce3c2 into main Jul 14, 2026
6 checks passed
@florivn
florivn deleted the fix/learninggoalhub-nginx-upstream branch July 14, 2026 11:17
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.

1 participant