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

[johnitvn]

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

[github-actions]

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]

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.