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

Argo CD Internal Server Error with TLS-enabled Ingress on Traefik #32084

Closed
johnitvn opened this issue Feb 20, 2025 · 2 comments
Closed

Argo CD Internal Server Error with TLS-enabled Ingress on Traefik #32084

johnitvn opened this issue Feb 20, 2025 · 2 comments
Assignees
Labels
argo-cd solved stale 15 days without activity tech-issues The user has a technical issue about an application

Comments

@johnitvn
Copy link

johnitvn commented Feb 20, 2025

Name and Version

bitnami/argo-cd 7.1.10

What architecture are you using?

None

What steps will reproduce the bug?

I deployed Argo CD using the Bitnami Helm chart with the following command:

helm upgrade argo-cd bitnami/argo-cd \
--namespace argo-cd \
--create-namespace \
--set server.ingress.enabled=true \
--set server.ingress.tls=true \
--set server.ingress.ingressClassName=traefik \
--set server.ingress.hostname=argocd.local \
--set-string server.ingress.annotations."cert-manager\.io/cluster-issuer"=cluster-issuer

What is the expected behavior?

Argo CD should be accessible without the "Internal Server Error" issue when using TLS-enabled Ingress.

What do you see instead?

When I visit local domain I see "Internal Server Error"

Additional information

  • I am using Traefik as the Ingress Controller.
  • I have successfully deployed another application (WordPress) with similar Ingress configurations, and it works without any issues.

Here is the command I used to deploy WordPress:

 helm install my-wordpress bitnami/wordpress \
   --set service.type=ClusterIP \
   --set ingress.enabled=true \
   --set ingress.tls=true \
   --set ingress.hostname=wordpress.local \
   --set ingress.ingressClassName=traefik \
   --set-string ingress.annotations."cert-manager\.io/cluster-issuer"=cluster-issuer
@johnitvn johnitvn added the tech-issues The user has a technical issue about an application label Feb 20, 2025
@github-actions github-actions bot added the triage Triage is needed label Feb 20, 2025
@github-actions github-actions bot removed the triage Triage is needed label Feb 25, 2025
@github-actions github-actions bot assigned migruiz4 and unassigned carrodher Feb 25, 2025
Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Mar 13, 2025
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd solved stale 15 days without activity tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

4 participants