Contact
Get in touch
Email us directly, or use the public tracker where an answer helps the next person with the same question.
General enquiries
Anything at all — support, business, press, or a question you'd rather not ask in public. We aim to reply within a few working days.
Privacy & data requests
The named contact in our Privacy Policy — data-rights requests, questions about cookies or advertising on this site.
Before you write in: most technical problems have a known answer. The Troubleshooting guide covers the common failures symptom-by-symptom, and the FAQ answers the questions we get most.
Where to send what
Bugs & support
Something broken, erroring or behaving oddly in the agent. This is the main channel — it's where the maintainers actually are, and where fixes get tracked.
Open an issueFeature requests
An idea for the roadmap, a player we should support, or a rough edge worth smoothing. Search first — it may already be filed and under discussion.
Suggest a featureQuestions & discussion
Not sure whether something is a bug, or want to compare notes on hardware and player setups? Ask in the tracker — questions are welcome there.
Ask a questionSecurity reports
Found a vulnerability? Report it privately through GitHub's security advisories rather than a public issue, so it can be fixed before it's disclosed.
Report privatelyHow to report a problem well
A good report gets a fix in one round trip; a vague one costs three. If you're opening an issue about your instance, include as much of this as you can:
- The version you're on — it's at the bottom of your dashboard, and in Settings → Server.
- How you run it: Docker Compose, a Podman Quadlet unit, or something else — and on what (NAS, mini-PC, VPS).
- Whether you're in local mode or relay mode (Settings → Sources).
- What you expected to happen, and what happened instead.
- The relevant container logs — docker compose logs --tail=200 is usually enough.
- If it's a player problem: which app, and whether you connected by playlist or as an HDHomeRun tuner.
Please redact your API key, dashboard password and any source URLs you'd rather not publish — GitHub issues are public and indexed by search engines.
What we can and can't help with
Things we can help with
- Bugs, crashes and unexpected behaviour in the agent.
- Setup that won't complete, or a dashboard that won't load.
- Connecting a player or media server.
- Feature requests and roadmap questions.
- Questions about this website, its privacy policy or its advertising.
Things we can't
- Supplying channels, playlists or sources — the software ships with none, and we don't provide any.
- Telling you whether a particular source is lawful where you live.
- Accessing, resetting or inspecting your instance — we have no route into it by design.
- Recovering a dashboard password. It's stored on your machine, hashed; reset it there.
Legal, privacy and abuse
Anything covered by our Acceptable Use policy — including a report that Rebel-operated infrastructure is being misused — should go to contact@rebeliptv.com. Requests under our Privacy Policy go to privacy@rebeliptv.com. Please use email rather than the public tracker for these, so you aren't publishing details you'd rather keep private.
Note that because Rebel IPTV hosts no content, there is no library here to take down. Content carried by a self-hosted instance is controlled solely by whoever runs it, and they are the right point of contact for it — we have no route into anyone's instance.