is it possible with Streamio to stream to WAN?
is it possible with Streamio to stream to WAN?
What else is the "remote HTTPS connection"? Is it possible to stream my stream OUTWARDS to WAN? (With port forwading) So I can just give friends a link to stream from my stream? Easy peasy? Would be super handy
If I remember correctly they added this feature right around the time they announced Stremio Web (basically their web interface/web-app).
The web-app was mainly intended for devices that cannot download the fully fledged app (coughIOS....cough). I think this "remote HTTPS connection" is related to that: You basically have the fully fledged Stremio app on one device, the limited web-app on another device, and use this remote server setting to give the web-app all the missing features as long as you have the fully fledged Stremio app running on one device. Never got it to work though.
Maybe this helps:
If you want to "share" you stream to friends, you could also look into the Peario add-on. They don't need to have Stremio installed, share the Peario link, press ready and you're done. Didn't manage to get subtitles working though.
Edit: correction about Peario.
At this point just use streamio-web. Make the server go through a vpn and all your apps will be protected. Then just make the server public. (Although a warning about making services like this open to the whole web is probably needed)
im not sure what the difference is between stremio-web and this https connection method. I installed Caddy as a reverse proxy, but when I connect to my IP in the browser, I get redirected to this URL:
Why am I using their DNS or site? I'm so confused. I thought my Stremio + Caddy would connect me INDEPENDENTLY over the interwebs
How does stremio compare vs running your own jellyfin/radarr/sonarr locally? I only pay $1/month for a VPN to torrent public torrents, and anything I want I can find pretty easy.
And yeah, I believe remote https connection can be streamed outwards to WAN.
just thought Stremio might be quicker and easier, because you can just give one temporary link to friends, without much setup on their side. [If it works at all.] I'm not that familiar with WAN on Jellyfin or Plex, but I doubt it is easier than just giving a link they can just stuff in VLC / MPV / (a browser?). Any idea how the experience is for an outsider/guest to whom you want to share something with on jellyfin/radarr/sonarr ?
In practice, I'd more often than not share with absolute tech morons
Fair.
Remote HTTPS connections through stremio are going to need some sort of certificate; it's likely you'll have to run a reverse proxy through caddy or something to let people easily access it from the outside.
For friends - I set them up a user on jellyfin and point them at media.mydomain.com and they get ... essentially a netflix interface. I tell them their username and password, and they just use it like plex/netflix.
Yes you can and its super easy. Setup your conection through HTTPS block your port only locally, buy a 1$ domain and install cloudflared tunnel. (Cloudflare configures your own TLS.)
You should disable the instance, or try to modify some parameters so you have to connect via some login or password.
I don’t use Streamio, but I’d be really surprised if that wasn’t what that was for. Other software I’ve used (though not for media) has the same option, and that’s exactly what it does.
I see, so im not crazy, probably. But any idea what I should enter in the "Override the streaming server URL"? My internal ip / external ip ? Or is that something separate? (I actually think this is where the native player gets its stream from, so 127.0.0.1.)
I’m not sure. Do they have documentation or a wiki anywhere?
Your current setting is the “loopback” address. You’re listening for traffic to this address, and the only thing that can send to the loopback is yourself. This is a safe default, it means only the computer running the software can talk to it. Generally 0.0.0.0 listens on all available addresses. If that doesn’t work, use your local / internal ip.
This ui smells like it’s trying to hide the implementation details, but that makes things extremely difficult when troubleshooting