Unable to load data: Request has been terminated Possible causes: the network is offline Origin is not allowed by Access-Control-Allow-Origin the page is being unloaded, etc. about argo-cd

[UriZafrir]

Hi, I think I have the same issue.
redirect goes from settings to version many times and finally fails

[csyyy106]

help ME

[rouke-broersma]

Usually happens when the UI can't reach the backend api, like when argocd-server is restarting or if your port-forward bugs out or something like that.

[csyyy106]

Hi, I think I have the same issue. redirect goes from settings to version many times and finally fails

Have you found a solution yet？

[UriZafrir]

Actually yes.
You need to add an annotation to the ingress-nginx:
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"

Its actually documented here
https://argo-cd.readthedocs.io/en/stable/operator-manual/ingress/
Look for "redirect loop"
This is the thread i found that talks about it
#2953 (comment)

[powellchristoph]

Actually yes. You need to add an annotation to the ingress-nginx: nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"

Its actually documented here https://argo-cd.readthedocs.io/en/stable/operator-manual/ingress/ Look for "redirect loop" This is the thread i found that talks about it #2953 (comment)

For the record, I have the following Nginx annotations and I still get the error.

      nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
      nginx.ingress.kubernetes.io/ssl-passthrough: "true"
      nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
      nginx.ingress.kubernetes.io/cors-expose-headers: "*, X-CustomResponseHeader"