-
Notifications
You must be signed in to change notification settings - Fork 9
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 (HTTP & HTTPS) while loading app #10
Comments
Also, if I connect directly to the webrtc I get this: |
Ok progress... If I add
How do I redirect the ws address to HTTPS too? @oparoz |
When running with Opera I get this in the browser log:
|
Ok another update.... Added this in my NGINX conf
...and now it works if I allow insecure scripts. |
Ok, strange, now I get this:
Same settings as latest post. |
(Removed Spreed Me) Any ideas? |
You cannot use the snap using HTTP only, so I think that the problem here is your reverse proxy. You also cannot access Spreed.ME directly. You have to use the app within Nextcloud. |
@oparoz I was thinking this is something that could be setup directly in the snap? I'm trying with the Nextcloud App, but it fails. Though I can reach the WebRTC directly over https... |
The snap has been simplified and the HTTPS routines for spreed.ME removed. It's designed to be used with a reverse proxy which handles all SSL requests and connects locally via HTTP. |
Hmm.. this is exactly what my Nginx Reverse Proxy does. How do you use it? Reported upstream as well --^ |
https://github.com/nextcloud/spreedme-snap#1-set-up-your-reverse-proxy |
Got it working again (updated the script a bit) and now I can use it as long as I allow insecure scripts, but I still get this in the browser log:
|
This solved it: nextcloud/vm@cf86ab9 |
Great. I need to collect a working NGINX config and add it to the readme so that others don't run into the same issue. |
It's easy, just do as I did in this thread. :) The issue was solved by not enforcinig the HTTPS ENV |
I'll just use this but enforcing HTTP: |
Yes, that's the Nginx config if you don't run Nginx as a Reverse Proxy, that were the case in this issue. |
@oparoz IRC please :) |
For everyone who has the same issue: My simple guide on how to fix this: TL;DR:
to your |
Steps to reproduce
Expected behaviour
SpreedMe should be shown
Actual behaviour
Screen is blank (WSOD) and gives me this output with the inspect tool (Chrome)
It's installed with the current VM script that can be found here and works locally but fails with my domain.. I should mention that I'm behind a Nginx Reverse Proxy that sends HTTP to my backends.
The text was updated successfully, but these errors were encountered: