Is HTTPS supported?See original GitHub issue
I have enabled HTTPS using Nginx Reverse proxy running a standalone instance but receiving some “Mixed content” errors. I’m not seeing anything in the config.yml or elsewhere to serve scripts over https. Is this not a supported feature?
Mixed Content: The page at 'https://<server_name>/' was loaded over HTTPS, but requested an insecure script 'http://<server_name>/graph/?targets=all&id=auto-1&fit=yes&type=multitarget&config=multitarget&source=latency.First%20Group'. This request has been blocked; the content must be served over HTTPS.
- Created a year ago
- Comments:17 (17 by maintainers)
Top GitHub Comments
Got this working now, thank you for the help!
@bile0026 am unable to reproduce with 1.4.3 installed and the config you pasted above
can you confirm that
pip freezecomes up with vaping installed as 1.4.3?
I forgot to upgrade vaping with pip, my bad. Looks like it will launch now without the error. Now I can get back to figuring out UWSGI, thanks!