-
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
Allow Enabling HTTPS with ENV Var #8
Comments
I've already added the 12470 port to the
See PR #13 |
I get |
Is this issue a reason why connection to the server fails unless it is exposed publicly over https (ex: https://stremio.domain.com)? Weird thing is when trying to set my server to point to 'http://192.168.1.2:11470' or 'https://192.168.1.2:12470' it fails to connect, but if I copy stream URL ( #19 ) and replace the malformed IP with aforementioned LAN IP video loads and plays, |
@damacchi I am currently having the same issue, did you manage to fix it? |
I think there's an undocumented (or hard to find) endpoint that generates the certs or i think you need to just put self signed certs in the settings directory. PEM file, i think. proto://localhost:11470/get-https |
I had to ensure the ipAddress was set in the query string for this to work. e.g
This then returned some json, e.g:
And created a httpsCert.json in the data dir with matching details. The domain it returns has an A record pointing to Accessing it in a browser redirects to app.strem.io with the correct streamingServer query string passed, and https certs all seem to be working |
I believe I found a way to persist the SSL certificate. Here is what I did: I added
Restarted the container and generated the SSL certificate like @tompipe mentioned;
In my case: I also got it working behind a reverse proxy; using nginx-proxy manager with Let's Encrypt certificates.
Here are my proxy host settings:
|
The server is able to create valid SSL certificates given a LAN IP, but there is no way to set this outside of the Stremio app settings. (when connected to the server)
I propose creating an env var (could be named "REMOTE_HTTPS") that should be set to the LAN IP address in order to provide an SSL certificate for it.
The HTTPS server uses the 12470 port, while the HTTP server uses the 11470. (only 11470 is currently being exposed in this docker image, I believe)
The text was updated successfully, but these errors were encountered: