Need help debugging decentralized Quran audio streaming with WebTorrent

I'm working on a new decentralized audio streaming app using WebTorrent to deliver Quran audio without relying on centralized servers. For this, I’ve built two open-source projects:

Open Quran

An open-source Quran app built with Next.js and hosted on Vercel. It’s designed to provide an optimal Quran audio streaming experience across platforms. Audio content is distributed via WebTorrent in the browser, meaning it relies on WebRTC peers or web seeds—traditional TCP/UDP torrent seeds are not supported.

Open Quran Tracker & Seeder

This repo includes two Dockerized services:

1. Tracker: A self-hosted WebTorrent tracker acting as a private WebRTC bridge to connect browser peers.

2. Seeder: A torrent seeder that continuously seeds all Quran audio files to speed up availability and streaming.

The issue

While streaming works perfectly with public torrents like the Ubuntu ISO (plenty of seeds), Quran audio streaming fails or stalls. I suspect it's due to insufficient WebRTC-compatible peers or missing web seeds. Since WebTorrent in the browser can't connect to traditional torrent clients, the network needs more compatible peers (like other browsers or my custom seeder).

How you can help

• Test the Open Quran app

• Check if the torrents load for you

• Suggest improvements for peer seeding or WebRTC connectivity

• Help debug the seeder or tracker setup

Any help from those familiar with WebTorrent, browser P2P, or decentralized distribution is appreciated. Let’s push forward a censorship-resistant and scalable way to share Islamic content.

Thanks in advance!