-
Notifications
You must be signed in to change notification settings - Fork 25
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
Https is not properly detected #42
Comments
Which port did you forward to your reverse proxy? I think you need to forward the https port ( This will probably also require you to skip the tls verify in your reverse proxy. Alternatively, you can generate the tls cert with the Alternatively, use this other docker image which has everything assembled. As an example, this is in my Caddyfile. I am not familiar with other reverse proxy, so will not be able to help you.
The streaming server shows "Online" in my setup, but still jumps to "Error" at times, so I am not confident my configuration is working 100%. |
I have the same issue and I don’t want to use stremio https port as there is no need for tls between traefik and stremio. I’ve tried looking for server.js GitHub to open PR but I cannot find it. Where is it? |
I believe it comes from here. https://github.com/Stremio/stremio-service/blob/master/src/server.rs |
Does it? Using default port 11470 as a random search criteria, I don’t find it mentioned in that repo, it doesn’t look the same as that server.js |
I'm not familiar. The following issue also discussed the sources |
Thank you! I’ll follow up on that one |
I serve stremio server behind a reverse-proxy with https
My server is available at:
https://stremio.server.com
if I open app.strem.io and specify https://stremio.server.com/ as my server then everything works perfectly
if I open https://stremio.server.com/ then the server is pre-populated to http://stremio.server.com/ (http instead of https) and the app doesn’t work.
If it’s not possible to detect http/https then I suggest to add a separate environment setting to provide a proper url.
The text was updated successfully, but these errors were encountered: