Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx container will not listen on IPv6 #636

Closed
mdallaire opened this issue Sep 25, 2024 · 2 comments · Fixed by #639
Closed

Nginx container will not listen on IPv6 #636

mdallaire opened this issue Sep 25, 2024 · 2 comments · Fixed by #639
Labels
2. developing Work in progress nginx container issues related to the nginx container bundling in the nextcloud pod.

Comments

@mdallaire
Copy link
Contributor

Describe your Issue

I am trying to run the chart on a cluster with IPv6 enabled, but the nextcloud pod never completes because of failed startup probe for the nextcloud-nginx container.

The generated default configuration when nginx is enabled only sets the port to 80 which defaults nginx to listen only on IPv4

Logs and Errors

Startup probe failed: Get "http://[2606:re:dac:ted::1:1697]:80/status.php": dial tcp [2606:re:dac:ted::1:1697]:80: connect: connection refused

Describe your Environment

  • Kubernetes distribution: Talos v1.7.6

  • FluxCD v2.3.0

  • Helm Chart Version: 6.0.2

  • values.yaml:

# paste your values.yaml (anonymize any sensitive data)

Additional context, if any

I just recently switched my cluster from IPv4 to dual-stack. I have had the same issue with other deployment and usually changing the listen address to [::]:80 when using nginx resolves the issue.

Unfortunately, the way the chart generates the default configuration overrides the /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh of the nginx:alpine container.

I might submit a PR to the chart to try and fix this by adding a new value, something like nginx.listenAddress that could be used in charts/nextcloud/files/nginx.config.tpl with the containerPort value.

@jessebot
Copy link
Collaborator

Ohhh, @mdallaire, that might be a good idea!

@wrenix, you were just working on cleaning up some more nginx stuff in #630, so you've had a recent look at the state of things. This sounds like a good idea right? I personally haven't touched ipv6 with nextcloud yet, but this is all fascinating to me regardless :)

@jessebot jessebot added 0. Needs triage Pending approval or rejection. This issue is pending approval. nginx container issues related to the nginx container bundling in the nextcloud pod. labels Sep 25, 2024
@jessebot jessebot added 2. developing Work in progress and removed 0. Needs triage Pending approval or rejection. This issue is pending approval. labels Sep 26, 2024
@wrenix
Copy link
Collaborator

wrenix commented Oct 1, 2024

@jessebot my PR is not involved in that part of Codes.
@mdallaire thanks for creating that PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. developing Work in progress nginx container issues related to the nginx container bundling in the nextcloud pod.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants