This feels highly manipulative. I have already "said thanks" by completing my own part of the transaction - paying for the service. Now, GTFO please.
First of all, a big thank you to the developers for this project. The "light" version is impressively efficient compared to the original.
TL;DR: I am routing torrentio.strem.fun through a SOCKS5 proxy (home OpenWRT) because my VPS IP is blacklisted. However, because Torrentio returns RD links "wrapped" in its own domain, MediaFlow is accidentally routing the entire media stream through the SOCKS5 proxy instead of just the metadata. This triggers RD's "concurrent IP" security, risking a ban.
Full: I am running my stack on an Oracle VPS (AIOStreams, Torrentio, Real-Debrid, and MediaFlow Proxy Light). Since Torrentio blocks Oracle IPs, I route all Torrentio traffic through a SOCKS5 proxy hosted on my home OpenWRT router using MediaFlow's transport routes.
The Technical Failure: Everything appeared to work, but an audit of the SOCKS5 traffic reveals that MediaFlow is funneling both the metadata AND the RD Video Stream through the home proxy server.
real-debrid.com/d/xxx); it returns a "wrapped" link (e.g., https://torrentio.strem.fun/real-debrid=TOKEN/...).torrentio.strem.fun domain in the URL, matches it to my SOCKS5 transport route, and dutifully tunnels the subsequent media request through my home router.The Question: How can I configure MediaFlow or AIOStreams to "unwrap" or resolve the Torrentio redirect before applying the transport route? I need to use the proxy only for the initial metadata scrape, while the actual media resolution/playback should happen directly from the VPS IP to RD.
Has anyone successfully decoupled "Proxied Scraping" from "Direct Playback" in this specific environment?
I've tried to surgically route only the Torrentio metadata through my proxy (...strem.fun/stremio ; ...strem.fun/manifest.json), however, this fully breaks the playback.
Received the unit on March 3rd, tested for an hour, and then charged to 100%. Been using it lightly for gaming & calls, and moderately to heavily for music ever since, almost daily. It's May 1st today, and the battery is just about to die (4%).
I am not sure how did the previous gen perform in this regard, but it's a relief to know I don't need to charge these weekly.