After accepting a self-signed certificate, the browser complains that scripts are being served in mixed mode:
Mixed Content: The page at 'https://<host>/browser' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://<host>/home'. This request has been blocked; the content must be served over HTTPS.
This error might occur when you use Apache
mod_proxy at your environment and external connection is secured, but internal one is not.
In this case the embedded Jetty webservice doesn't recognize that all external connections should be served in secured mode (over HTTPS) and keeps responding over HTTP.
User > HTTPS > Apache mod_proxy > HTTP > Datameers Jetty
In order to fix the issue, adjust Apache, Jetty, and Datameer settings.
ApacheAdd the following line to the Apache config for the Datameer
RequestHeader set X-Forwarded-Proto "https" env=HTTPS
datameer-install-path>/etc/jetty.xmluncomment the following:
DatameerMake sure that the correct hostname and protocol is set in <
# Define the address and port used to connect to DATAMEER. system.property.server.address=<host>:<port>
Restart Datameer and Apache to apply changes.