NGINX HTTP routing to services not working on initial deploy
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure, networking
Research direction
Start by redeploying the stack and checking the NGINX container log, then repeat the check after restarting that container. Inspect the NGINX configuration and the proxy endpoint resolution for the sabredav and calendarfeed containers. Done means both services are routed correctly immediately after deployment without an NGINX restart.
Written by the indexing model from the issue text.
Description
It can be observed, that after deployment the routing defined in the NGINX configuration is not applied properly. The requests to the sabredav and calendarfeed container are not routed as defined in the configuration, causing "Primary script unknown" errors in the NGINX log. After restarting the NGINX container the routing works.
The issue can be obeserved by redeploying the stack, and checking the NGINX container log.
This issue might be related to DNS caching inside the NGINX container, since the given proxy endpoint is resolved once on start. See linked article.
https://serverfault.com/questions/1117412/nginx-serving-content-from-wrong-proxy
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Run the dependency drift checkPossibly taken @spaceninja claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cloudfour/lighthouse-parade#449 ·
Maintainers usually reply within 1 day
-
Run the dependency drift checkPossibly taken @spaceninja claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
cloudfour/stylelint-config-cloudfour#683 ·
Maintainers usually reply within 1 day
-
good first issue help wanted new check
Difficulty 2/5 3-5 days Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dorianleveque/nixos-config#140 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100