-
Notifications
You must be signed in to change notification settings - Fork 16
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 issues #11
Comments
Hi, |
I'm running the image behind a nginx reverse proxy because I have multiple services on the same server. |
Have you tried to configure in Bludit settings the domain with the |
no. because of the mixed content issues I can't access the admin panel :/ I guess it has something todo with the whole setup and how the nginx reverse proxy takes care of SSL certificates. |
I ran into the same problem when using nginx-proxy. I solved it by initializing bludit via http. Disabling https redirection can be done with these environment variables:
If you visited the page before, you need to clear the HSTS cache in order to access the unsecured page. Other nginx proxy solutions should have similar options. |
I stumbled accross some issues with the docker container.
Firefox as well as Chrome prohibit the use of mixed content from http and https sources.
the bludit image apparently uses http for internal ressources.
My quick and dirty fix was to add
add_header Content-Security-Policy "upgrade-insecure-requests;"
to default.conf in the running docker container.
If I'm not mistaken this will only solve the issue for modern browsers though, long term it would probably be better to upgrade the internal ressource loading to https.
I tried to open a pull request to implement this fix, but couldn't.
Would be very cool if this would be implemented. Just following the setup instructions doesn't lead to success in a production environment.
The text was updated successfully, but these errors were encountered: