400 Bad Request - The plain HTTP request was sent to HTTPS port

cloudflare / cloudflare-ingress-controller

A Kubernetes ingress controller for Cloudflare's Argo Tunnels

Apache License 2.0

364 stars 55 forks source link

Open lorddaedra opened 5 years ago

lorddaedra commented 5 years ago

But in my case I prefer to use http2 for performance (https://imagekit.io/demo/http2-vs-http1) and security (mitm) reasons...

I see error 400 Bad Request - The plain HTTP request was sent to HTTPS port

I use Cloudflare Origin Certificates for my services...

Also I enable Automatic HTTPS Rewrites in Cloudflare panel.

I do not expect to see any plain http requests here... How to fix it?..

skilledboy commented 4 years ago

Hi @lorddaedra , could you solve your problem? The same thing is happening to me, any idea how to solve it? Thanks

xunholy commented 4 years ago

I've also run into this issue - anyone found a reason why or how to solve it?

lorddaedra commented 4 years ago

@skilledboy I am sorry to have kept you waiting for so long.

@ here I do not use cloudflare-ingress-controller anymore. (I use Google Cloud Run service for most of my projects...)

skilledboy commented 4 years ago

thanks @lorddaedra , I am particularly a fan of Google Cloud Run, but unfortunately it is not useful for me to expose my services from my raspberry pi 4 cluster. For this reason I use https://developers.cloudflare.com/argo-tunnel/reference/kubernetes

I leave you an image of how I mix everything (Cloudflare argo tunnel, kong gateway, etc ...).

Sorry, my english is very bad

zackbloom commented 4 years ago

We are currently more focused on improving the cloudflared client itself, leaving this ingress controller deprecated. You can read more here: https://github.com/cloudflare/cloudflare-ingress-controller/issues/172#issuecomment-541230988