P2P streams do not appear on Android clients (official and self-hosted instances)

[WildStar2022]

Hello,

I've been testing Magnetio in P2P-only mode (no debrid provider configured) and have been unable to get any streams to appear.

Tested environments

Clients

Google TV Streamer (Stremio 1.10.4 / Server 4.21.0)
Older Samsung Android tablet

Magnetio

• Official hosted instance
• Self-hosted v1.1.5 (Docker, Redis, nginx reverse proxy)

Results

In all four combinations:

• Magnetio installs successfully.
• Torrentio works normally.
• No Magnetio streams are displayed.

Self-hosted logs

The server consistently reports that it finds and returns P2P streams, for example:

records=115
filtered=50
base=50
final=10
direct=0
p2p=10

I also verified that the /stream/...json endpoint returns stream objects containing infoHash, fileIdx, tracker sources, and behaviorHints.

I have not tested with a debrid provider, so I can't determine whether this is specific to P2P-only mode or affects Magnetio more generally.

Thank you!

[peterdsp]

Hi @WildStar2022,

Thanks for the detailed report! PR #116 addresses the P2P stream visibility issue with several targeted fixes:

Root cause: fileIdx defaulting to 0
When no specific file index was available, Magnetio was setting fileIdx: 0 on every stream object. On Android clients (and some others), this causes playback failures on single-file torrents because the client tries to select file 0 instead of auto-detecting the video file. This is now fixed — fileIdx is omitted when not explicitly known, letting the client handle file selection.

Tracker initialization race condition
The server was accepting requests before the tracker list was loaded, so early requests got empty tracker lists → P2P streams had no sources → many clients silently dropped them. The server now waits for trackers to fully initialize before accepting any connections.

New: P2P Privacy Proxy (optional)
PR #116 also adds an optional server-side torrent streaming proxy. When enabled, streams are returned as HTTP URLs instead of infoHash objects — which means they work on all Stremio clients regardless of P2P support. This completely bypasses the client-side torrent stack, and as a bonus, hides user IPs from torrent swarms.

Speed improvements
Stream loading is significantly faster: stale-while-revalidate cache returns cached results instantly, scraper concurrency doubled, timeouts halved, and faster early return with fewer minimum results required.

These changes are in PR #116, pending merge. Once merged, they'll auto-deploy.

[WildStar2022]

Hi Petros,

I rebuilt Magnetio from the latest main after PR #116 was merged. I restored my local changes, performed a clean rebuild, flushed the Redis cache, and restarted the containers.

Unfortunately, there was no change in behavior. The addon logs still show P2P results being returned (e.g. final=10 p2p=10), and the /stream/...json endpoint returns valid stream objects with infoHash and tracker sources. However, Magnetio still displays no streams on either my Google TV Streamer or my Samsung Android tablet.

---

Update - Additional testing

I tested with the latest Windows desktop client (6.0.1-beta.09) as well as the two Android. devices.

The behavior is identical on both platforms.

The Magnetio addon receives the request and logs successful results. For example, when requesting The Matrix (tt0133093), the addon reports:

records=88
filtered=50
base=50
final=10
direct=0
p2p=10

Torrentio streams are displayed normally, but Magnetio streams are never displayed, despite the addon reporting that it found and returned 10 P2P streams.

[peterdsp]

Hi @WildStar2022,

Thanks for the follow-up testing. I found the likely root cause — PR #118 (just merged and deploying now) adds an explicit dht:<infoHash> source entry to every P2P stream object.

What was happening:
Magnetio's buildSources() only returned tracker: prefixed URLs in the sources array. Torrentio (which works fine on your devices) includes both dht: and tracker: entries. Some Stremio clients require the explicit dht: source to enable DHT peer discovery — without it, the stream objects are technically valid but the client silently drops them because it can't resolve peers.

The fix:
Every P2P stream now includes dht:<infoHash> as the first source, followed by tracker URLs. This matches the format that Torrentio and other working addons use.

Workaround (available now):
If the DHT fix doesn't resolve it, you can enable the Privacy Proxy in your addon configuration. When enabled, streams are returned as HTTP URLs instead of P2P infoHash objects — completely bypassing the client-side torrent stack. This works on all clients regardless of P2P support.

The deploy should complete in ~3 minutes. Please test again after and let me know!

[WildStar2022]

I've updated to PR #118. The dht: source is now present in the returned JSON exactly as described, but the original problem remains. Stremio still shows only Torrentio streams.

Note: It would have been best not to close this issue (or any others, for that matter) until I or someone else had confirmed that the issue I had taken the time to report was actually resolved. Good luck!

[cr0wm4n]

Hi, I have been fighting to get this working for the past 4 or 5 days and I am in exactly the same position. trying from both my TV and laptop i get no results returned however the docker logs are showing results getting returned. I use another older jackettio addon from here https://github.com/arvida42/jackettio/pulls and i manually added the pull for P2P. this works fine on any device I have tried so far. But no matter what I do I cannot get Magnetio to pass a list to the clients.

[peterdsp]

Reopening this — it was auto-closed by the "Fixes #111" link when PR #137 merged, but per @WildStar2022's request it should stay open until the fix is confirmed on real devices.

Root cause (confirmed against the live deployment and diffed against Torrentio's stream object):

1. Magnetio emitted a description field on every stream; several Stremio clients (Android, Google TV, Windows 6.0.1-beta) silently drop stream objects that carry it, so the whole list rendered empty.
2. sources (the dht:/tracker: peer-discovery hints) were missing — a regression from Fix stream integrations and recover production without media disk #124, which removed the buildSources() added in Fix P2P streams not showing on some clients (#111) #118.

PR #137 removes description (keeping title) and restores buildSources(), so the object now matches Torrentio's known-good shape. It's merged and deploying now.

@WildStar2022 @cr0wm4n once the deploy lands (~a few minutes), please flush the Redis cache, reload, and confirm whether Magnetio streams now appear. I'll leave this open until you confirm.