Confirm public IPv4
Identify the public IPv4 address your streaming server uses when it requests upstream channels. Paid access is tied to whitelisted public IPv4 addresses.
Guides
Server Setup for IPTV Restream
General technical guidance for preparing your IPTV server or panel before trial or paid activation. Software-specific commands are pending verification.
Preparation
Setup checklist for operators
Use these steps to prepare your infrastructure before requesting a trial or completing paid activation.
Note load balancer IPs
If traffic exits through a load balancer or gateway, whitelist those public IPv4 addresses as well — not only private or internal NIC addresses.
Plan concurrent pulls
Estimate how many live channels your panel will pull at once. That estimate should guide which monthly connection plan you choose.
Prepare playlist import
Plan how you will import an M3U / HLS playlist into your panel or media server. Exact UI steps vary by software and version.
Submit IPs for whitelist
Send the correct public IPv4 list to support via WhatsApp when arranging paid activation. See the IP whitelisting guide for what to include.
Test playback carefully
After access is arranged, test a small set of channels first. Confirm playlist load, stream open behaviour, and concurrent pull limits before scaling up.
Networking
Public IPv4 requirements
Paid Restream access is limited to approved public IPv4 addresses. Your server must present a stable public IPv4 when it requests upstream channels.
Residential or frequently changing addresses are not assumed. If your host renumbers public IPs often, contact support before purchase so expectations are clear.
- Prefer stable server or datacenter public IPv4
- Include every egress IP that pulls streams
- Document load balancer public IPv4 when used
Identifying server and LB IPs
Check the public IPv4 your host assigns to the streaming node. If a load balancer, NAT gateway, or proxy handles outbound traffic, record that public IPv4 instead of (or in addition to) the private backend address.
IPv4 vs IPv6
Do not assume an IPv6 address substitutes for a required public IPv4 whitelist entry. Confirm with support which addresses will be used for outbound stream pulls.
Delivery
M3U / HLS integration concepts
After access is arranged, you typically receive playlist access for use with an IPTV panel or media server. The playlist lists channel entries; the player or panel requests media segments as needed.
Exact import paths, field names, and refresh options differ by software. Until panel-specific instructions are verified, use your vendor’s documentation for playlist import and keep credentials private.
M3U / HLS guideCapacity
Concurrent connection planning
Each concurrent upstream channel pull counts toward your plan. Estimate peak simultaneous channel opens — not total viewers — when choosing a package.
Example: pulling 40 distinct live channels at once may consume about 40 upstream connections, even if many viewers watch through your redistribution layer.
Connections explainedGo-live
Whitelist submission and playback testing
Paid activation is manual. Submit accurate public IPv4 details, complete payment verification when purchasing, then test carefully.
Submit via WhatsApp
Message support with your plan choice and the public IPv4 addresses that will pull streams. Use verified contact channels only.
Confirm activation
Wait for support to confirm whitelist and access details. Do not assume automatic activation after sending an IP list.
Test playback
Import the playlist, open a few channels, then increase concurrent pulls toward your expected load while watching for errors.
Watch-outs
Common configuration issues
These problems appear often during first setup. For deeper diagnostics, use the troubleshooting guide.
Wrong IP submitted
Submitting a private LAN address, IPv6-only address, or an unused secondary IP often results in access failures after whitelist activation.
Load balancer mismatch
If outbound requests leave through a balancer whose public IPv4 was not whitelisted, streams may fail even when the origin server IP looks correct.
Over-pulling connections
Opening more concurrent upstream channels than your plan allows can cause refusals or unstable behaviour on additional pulls.
Credentials shared insecurely
Playlist URLs and access details should stay private. Do not post them in public forums, tickets visible to third parties, or unsecured documents.
FAQ
Server setup questions
Not on this page. Provider- or panel-specific CLI and UI steps are marked pending verification so we do not publish unverified commands. Support can discuss your stack after you contact WhatsApp.
Paid Restream access relies on public IPv4 whitelisting for your streaming servers and relevant load balancers. See IP Whitelisting.
After support arranges trial or paid access and you have imported the playlist. Start with a limited channel set, then increase concurrent pulls toward your planned load.