Thank you for the response! I will look at my browsers dev console.

Okay. Chrome says this: knivesandchives-llc-receipt-1:414 Mixed Content: The page at 'https://nixtamalized.com/slides/slide/knivesandchives-llc-receipt-1' was loaded over HTTPS, but requested an insecure resource 'http://nixtamalized.com/slides/embed/1?page=1'. This request has been blocked; the content must be served over HTTPS. Firefox says this: Blocked loading mixed active content "http://nixtamalized.com/slides/embed/1?page=1"[Learn More]

Ermin, Where do I find the system parameter website.url ? I bet I haven't set it to https. Is it under "Website Admin" -> "Configuration" -> "Website name" ? I have this set to "nixtamalized.com", and neither http or https

I found a setting under "General Settings" with "Website" and it was configured "http://nixtamalized.com" so i changed that to https

But, in my case at least, it does not help...(I have deleted the PDF and uploaded it anew).

I get a new error: UnexpectedResponseException: Unexpected server response (301) while retrieving PDF "https://www.twanda.ch/slides/slide/7/pdf_content"

that didn't change anything. i uploaded a new pdf and that didn't work. PNG's appear to be working though! I can make my PDFs into PNGs for now.

Under "Website Admin" -> "Slides - Channels" -> "Public Channel" -> each message that logs what i've done in this Slide Channel has http and not https for the item.

I'm still trying to find a way, but I suppose it is a bug, in version 9.0 it works flawlessly. It is also not possible to create a slide in the backend, this results in a 500 server error :-(

I'm on version 9 :(

Where exactly is the system parameter website.url ?

Well, you are right, in my case it only works for 9.0 because it is a test server, which is not yet SSL secured. You can find the parameter web.base.url under Settings/Technical/Parameters/System Parameters. You need to activate the developer mode in order to access these settings.

Maybe this could point to a solution: https://github.com/mozilla/pdf.js/issues/6446

Ermin, You are the best!! That fixed it right up. Changing web.base.url to be https!!

My nginx configuration already has that setting in it -- here it reads in nginx: location / { proxy_pass http://openerp; # force timeouts if the backend dies proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504; proxy_redirect off; # set headers proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; }

Your site still tries to load from http:// instead of https://. So I assume that something in your proxy conf does not work properly. Try to check with other nginx configurations on the internet. I have Apache and after the change in my virtual hosts configuration, a restart of Apache and a reload of the website it worked immediately and all contents are now loading from https://.

I don't know how it could make a difference, if any, but I have dbfilter activated in my odoo-server.conf and installed the module https://www.odoo.com/apps/modules/8.0/dbfilter_from_header/

Andy, just a stupid question (but I had a conversation with somebody, who had this problem): have you set "proxy_mode = True" in your Odoo config file?

Chrome's error message is now: Mixed Content: The page at 'https://nixtamalized.com/slides/embed/6?page=1' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://nixtamalized.com/slides/slide/ein-number-6/pdf_content'. This request has been blocked; the content must be served over HTTPS. 6:1 Uncaught (in promise) UnexpectedResponseException {name: "UnexpectedResponseException", message: "Unexpected server response (0) while retrieving PD…s://nixtamalized.com/slides/slide/6/pdf_content".", status: 0}

Andy, see my last comment, it seems to be a CORS (Cross Origin Ressource Sharing) issue. Besides the link I have already posted in this comment, this one should be helpful also: https://awesometoast.com/cors/ But I was not successful so far...

I GOT THE SOLUTION!!!! Forget about CORS. You need to set the RequestHeader set "X-Forwarded-Proto" "https" in your virtual host conf in your proxy server, see the following sample for Apache: https://www.odoo.com/de_DE/groups/community-59/community-13327850?mode=thread