Mixed Content Error Troubleshooting (Community)

View the original community article here

Last tested: Aug 31, 2018
 

Scenario:

If your instance is self-hosted and is embedding Looker in an iFrame, and is receiving the following error:

Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure resource ''. This request has been blocked; the content must be served over HTTPS.

Possible Causes:

• You have a load balancer (ex. Nginx) that is managing your SSL certificates

Troubleshooting:

• Remove the -- no-ssl startup option
  • https://docs.looker.com/setup-and-management/on-prem-install/looker-startup-options
• Replace the no-ssl startup option with--ssl-provided-externally-by=<s>
  • Replace the <s> with the host and port of their external SSL provider
  • Make sure you have the = sign!
• Check your nginx settings against what we recommend here: https://docs.looker.com/setup-and-management/on-prem-install/sample-nginx-config. In particular, we have had customers set configured to set request headers that tell Looker what happened when forwarding the request as X-Forwarded-Prot
• Users have successfully updated their nginx settings by adding a rule in the nginx for the proxy_redirect from http:// to https://