Unknown error (200): Http failure during parsing for https://<site>/api/v1/csrftoken/login

[noelashford]

What happened?

I use an ingress controller to access the dashboard and even thought the backend and frontend are https, it seems to think there is an HTTP parsing issue somewhere ? <site. is obfuscation for the actual site.

What did you expect to happen?

I should be able to browse the dashboard.

How can we reproduce it (as minimally and precisely as possible)?

Create a backend https ingress w front end HTTPS as well, you will see this: Unknown error (200): Http failure during parsing for https://<site>/api/v1/csrftoken/login

Anything else we need to know?

The ingress is as follows:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
    cert-manager.io/cluster-issuer: letsencrypt-production
  generation: 1
  name: dashboard
  namespace: kubernetes-dashboard
spec:
  rules:
  - host: <site>
    http:
      paths:
      - backend:
          service:
            name: kubernetes-dashboard-kong-proxy
            port:
              number: 443
        path: /
        pathType: Prefix
  tls:
    - hosts:
      - <site>
      secretName: k8s-dashboard

What browsers are you seeing the problem on?

Chrome

Kubernetes Dashboard version

current

Kubernetes version

Client Version: v1.25.0 Kustomize Version: v4.5.7 Server Version: v1.23.3

Dev environment

No response

[TheoMorkel]

Is there any update on this issue? I am experiencing it as well.

[floreks]

That does not look like an issue on our side. Most likely it's a configuration issue on your side.

[noelashford]

I'm not so sure it's a configuration issue. Backend https & front end and it is telling me there's an http error when the token is pasted in. Prior versions worked with the exact same config at least for me.

…

On Thu, Mar 28, 2024, 7:50 AM Sebastian Florek ***@***.***> wrote: That does not look like an issue on our side. Most likely it's a configuration issue on your side. — Reply to this email directly, view it on GitHub <#8829 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2QZ4J3NEEP4YN73DWL6GWDY2PYXDAVCNFSM6AAAAABFFSBJ6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUHE4TMOJYGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[floreks]

You could try checking for logs in auth pod. Right now I am unsure how it could originate on our side.

[garymm]

I'm seeing this also.

@noelashford which version worked for you?

I tried both 7.1.3 and 6.0.8 and seeing the same issue. Connecting via kubectl port-forward works fine. So I think maybe it has something to do with the hostname?

[tynianov1]

I had the same issue. Do we have any updates here? Thanks

P.S. logs for all related pods (dashboard, API, auth, metrics-scraper, kong) look good to me and I don't see any suspicious lines. Additionaly, when I try to send request to the https://{domain_name}/api/v1/csrftoken/login via the Postman it returns me the 200 status code.

[floreks]

Is there anything in the browser console/network tab in the dev tools that could help?

Another thing I can think of is that there is an issue with SSL passthrough. You might try adding the below annotations to the ingress.

    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"

This is our default ingress that I am using to expose it locally:
https://github.com/kubernetes/dashboard/blob/master/charts/kubernetes-dashboard/templates/networking/ingress.yaml

[juvivas]

i resolved this issue modifying the kong configuration.

kong:
  proxy:
    http:
      enabled: true

so my ingressroute target the kong service at 80 port

[meekara]

I have same issue and changing kong proxy http enable does not fix issue and no log in auth pod. I'm using traefik ingress.
It work with port forward as well.

[juvivas]

I have same issue and changing kong proxy http enable does not fix issue and no log in auth pod. I'm using traefik ingress. It work with port forward as well.
i used these parameters for helm installation

api:
  containers:
    args:
      - '--disable-csrf-protection=true'
web:
  scaling:
    replicas: 2
    args:
      - '--disable-csrf-protection=true'
kong:
  proxy:
    http:
      enabled: true

[thunko]

I was facing the same issue and thought it could have relation with this one here

I configured the same settings as above, except for the web container, which doesn't support the disable csrf argument:

# helm upgrade --install kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard --create-namespace --namespace kubernetes-dashboard --set 'api.containers.args={--disable-csrf-protection=true}' --set kong.proxy.http.enabled=true

Accessed the kong proxy service and authenticated with admin-user token.

[c0desurfer]

That does not look like an issue on our side. Most likely it's a configuration issue on your side.

Probably is, getting same error on fresh install.

[nevillelyh]

I ran into this as well and it works after clearing cookies.

[djereg]

In my case something went wrong at first try, and the /api/v1/csrftoken/login endpoint has returned the index page what is an html content and MY BROWSER CACHED IT, and every time the frontend called the enpoint, the response was returned from the cache. After disabling the cache it worked well.

Knowing this, you can imagine the 5 hours I spent the last night exploring this. But at least I was able to deepen my relationship with Ingresses and IngressRoutes.

[floreks]

This does not look like a bug on our side. Every comment with a solution indicates that. If there will be any evidence suggesting otherwise, we can reopen.

/close

[k8s-ci-robot]

@floreks: Closing this issue.

In response to this:

This does not look like a bug on our side. Every comment with a solution indicates that. If there will be any evidence suggesting otherwise, we can reopen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kk-technical]

I have same problem...but still in problem.....
I tried every method... not work...