-
Notifications
You must be signed in to change notification settings - Fork 26
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 (Nextcloud) #56
Comments
`proxy_pass https://$upstream:443;`
This looks wrong to me. It should be `proxy_pass http://$upstream;` (assuming your `spreedme.conf` gets loaded in `<VirtualHost 192.168.4.111:80>`)
|
@leonklingele Thanks for your sharp eyes. Even if I set it to
And if I allow insecure scripts it works, but works bad. It recognizes my user, but other users can't use it and connect to the same rooms etc, not tested that much though) Any ideas? |
@leonklingele Here is a testroom. |
Either use `RequestHeader set X-Forwarded-Proto 'https'` instead of `RequestHeader set X-Forwarded-Proto 'https' env=HTTPS` _or_ configure your Apache server to listen on `192.168.4.111:443` + revert to `proxy_pass https://$upstream;`
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't know if it's a bug or if my setup is wrong, but I'm trying to setup Spreed.Me on a Nextcloud server with Nginx Reverse Proxy in front and Nextcloud on a backend Apache server. This is my setup:
Vhosts
Nginx Vhost
Handles port 443 and 80
Apache Vhost Nextcloud
nextcloud.conf
Apache Vhost SpreedMe
spreedme.conf (As Include in Apache.conf)
Errors
Here are a good summary of all the errors: nextcloud/spreedme-snap#10
Summary
It seems like you need to implement wss so that I can get secure connections, or it's my config that are wrong. Can you please help me here?
Thanks!
The text was updated successfully, but these errors were encountered: