Playback fails with HTTP 400 — URL triple-encoding on stream filenames

[lamehillbilly]

Hey! Love the plugin, it's been working great for most content. Running into a playback issue on certain titles though.

What's happening:
When I try to play certain shows (Euphoria is the one I've been testing), Jellyfin/ffprobe gets a 400 Bad Request from AIOStreams. Looking at the logs, the stream URL has the filename triple-encoded — spaces become %252520 instead of %20, brackets become %25255B instead of %5B, etc.

Jellyfin log:

[ERR] MediaBrowser.Providers.TV.EpisodeMetadataService: Error in Probe Provider
MediaBrowser.Common.FfmpegException: ffprobe failed - streams and format are both null.

Probing stream via https://aiostreams.elfhosted.com/playback/kkW1wnky.../Euphoria%252520%252528US%252529%252520%2525282019%252529%252520-%252520S01E01%252520-%252520Pilot%252520%25255BWEBDL-2160p%25255D%25255BDV%252520HDR10%25255D%25255BEAC3%2525205.1%25255D%25255BEN%25252BFR%25255D%25255Bh265%25255D-FRESH.mkv?name=Euphoria

[https @ 0x74272f2a3e00] HTTP error 400 Bad Request

You can see the filename portion is getting encoded multiple times — %252520 is %25 (encoded %) + 20, which means %20 got re-encoded at least twice.

Setup:

• Jellyfin 10.11.6
• Gelato 0.26.6.8
• AIOStreams (ElfHosted public instance)
• TorBox as debrid provider
• Streams resolve fine on the AIOStreams/Stremio side — it's specifically the URL that Gelato constructs for ffprobe/playback that has the encoding issue

What I've tested:

• Happens on desktop web player and iOS (Infuse) — not client-specific
• The stream itself exists and works through Stremio directly
• Other content plays fine, seems to be titles with parentheses and special characters in the release name that trigger it

Is this a known issue? Any workarounds in the meantime?