-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Mixed content errors #10688
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
We don't test with reverse-proxies . Generally you will need to enbale proxy-protocol. |
Let's see if what I got is useful: I apologise the long post but details seems to break the code block. Let me know how to fix it and I'll edit the post. What happened: What you expect to happen: NGINX Ingress controller version
Kubernetes
Environment
Instalation Cluster info
How was the ingress-nginx-controller installed:
also the load balancer version:
Others
Also from the ingress logs:
Thanks for the attention |
Just to test, I installed a k3s VM (as k3s comes with Traefik ingress). The problem also happens in there. |
Hi all,
Sorry if this is not following the procedures of how to post my problem.
I am trying to self-host speedtest-tracker (https://github.com/alexjustesen/speedtest-tracker) and my system has a Raspberry Pi with Nginx Reverse Proxy and a VM with K0S, MetalLB and Nginx Ingress. The Raspberry Pi provides access to all my services (Proxmox, HA, ...) and passes to Nginx Ingress the services that are in Kubernetes.
The problem is that with speed-tracker the pages are not loading correctly if I use ingress. I get the
blocked:mixed-content)
Things I have tried so far:
Fix the Reverse Proxy: I added
proxy_set_header X-Forwarded-Proto $scheme;
in the Raspberry Pi and create a Load Balancer service in my deployment and it worked. That actually was the initial configuration (normally I test things with a Load Balancer and then go to Ingress).Remove the Reverse Proxy: I removed the entry and created one in /etc/hosts. Worked. That was just to check if there was any other issues with the ingress and that was not the case. I returned to use the Reverse Proxy afterwards.
Add annotations to the ingress of the application:
nginx.ingress.kubernetes.io/proxy-set-header: "X-Forwarded-Proto $scheme"
: Did not work.nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
: Makes the error:ERR_TOO_MANY_REDIRECTS
Edit nginx cmap:
Add
use-forwarded-headers: true
. Did not workHere are the links for comparison:
http://speedtest.eddienetworks.ddnsfree.com
http://speedtest_lb.eddienetworks.ddnsfree.com (Temporary)
Thanks
The text was updated successfully, but these errors were encountered: