http>>>https -- Mixed Content

[yossisht9876]

At the moment NiFi works and I can access it via the ingress host.

look like a Mixed Content issue - some of the "urls" are still in http and nifi is on https so i get "Mixed Content" error

The problem is that I can't configure any processor at all. Every time, when I click on "configure" I get this error:

Unable to communicate with NiFi Please ensure the application is running and check the logs for any errors.

error logs on the browser show:

The page at 'https://nifi-xxxx.como/nifi/?processGroupId=root&componentIds=471557be-017d-1000-5ab8-8e8a5dea2994' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://https/nifi-api/provenance/47e447d8-017d-1000-6a48-56f3ac07539e'.

This request has been blocked; the content must be served over HTTPS.

any idea's ? thanks @banzo

[murilolobato]

I'm facing the same problem, even when using the oficial docker image alone.

[degola]

Same issue here:

• I have a k8s cluster with an external HTTPS termination
• I have enabled K8s nginx ingress controller with a specific hostname terminated by SSL and the following ingress annotations to connect to a self-signed HTTPS service (Nifi in this regard):
  • "nginx.ingress.kubernetes.io/backend-protocol": "HTTPS",
  • "nginx.ingress.kubernetes.io/upstream-vhost": "nifi.nifi.svc"
• i can login and see the flow but i listing of items in a queue ends up requesting a URL http:// instead of https://
• kube-proxy forward and localhost:8443 works without issues

I wonder what's the right configuration is and/or if that's a bug, i have played around with a few variables in the values.yaml, e.g.:

• properties.externalSecure: true
• safetyValve.nifi.web.proxy and safetyValve.nifi.web.https.host

Any hints welcome if this is a configuration issue.

[github-actions[bot]]

This issue is stale because it has not seen recent activity. Remove stale label or comment or this will be closed.