Stalker Portal IPTV: What It Is and How to Set It Up

Stalker Portal is a middleware platform that sits between the IPTV content server and the end user's device. It handles authentication, content organization, EPG management, and the user interface for set-top boxes and emulator applications. Originally developed by Infomir as the companion software for their MAG line of IPTV set-top boxes, Stalker middleware became the industry standard for MAC address-based IPTV delivery. The platform was later rebranded as Ministra TV Platform, though the community still widely refers to it as Stalker Portal.

Understanding Stalker Portal matters for IPTV users because it defines how your device communicates with the server, what features are available in the portal interface, and how troubleshooting works when issues arise. This guide covers the technical architecture, the authentication and content delivery flow, device compatibility, and step-by-step setup instructions.

Stalker Portal Architecture

The Stalker middleware stack runs on a server (typically Linux-based) and consists of several components. The web server (Nginx or Apache) handles HTTP requests from connected devices. The PHP application layer processes authentication, content queries, and portal logic. A MySQL or MariaDB database stores device registrations, subscription data, channel configurations, and EPG information. A streaming engine (separate from the middleware itself) handles the actual video delivery.

When a MAG device or STBEmu app connects to a Stalker portal, the communication follows the HTTP protocol. The device's embedded browser loads the portal's JavaScript application from the server. This JavaScript app then makes API calls to the server for authentication, channel listings, EPG data, and stream URLs. The API endpoints follow a predictable pattern: /stalker_portal/server/load.php handles most data requests, with action parameters specifying the requested data type.

The portal's JavaScript application runs within a customized WebKit browser on MAG devices. This browser supports HTML5, CSS3, and JavaScript but lacks the full feature set of desktop browsers. STBEmu replicates this browser environment on Android, which is why the portal interface looks and behaves identically on both platforms.

Authentication Flow in Detail

The authentication sequence begins when the device sends an HTTP request to the portal URL with its MAC address included in the request headers. The server extracts the MAC address and queries its database. If the MAC address is found and the associated subscription is active, the server generates a session token and returns it to the device along with the portal's JavaScript application code.

The session token is stored as a cookie on the device and included in all subsequent API requests. Each API request is validated against the session token, which the server cross-references with the MAC address and subscription record. If the token expires (typically after 24 hours of inactivity) or the subscription status changes, the device must re-authenticate.

The server also tracks concurrent connections per MAC address. If a subscription allows one simultaneous connection and a second device attempts to authenticate with the same MAC address (a MAC spoofing scenario), the server either denies the second connection or terminates the first one, depending on the provider's configuration.

Content Delivery Through Stalker Portal

Once authenticated, the device requests content data through API calls. The channel list request returns JSON data containing channel names, category assignments, stream type indicators, logo URLs, and EPG channel IDs. The data is organized by category, and the portal's JavaScript application renders it as the familiar grid or list interface.

When a user selects a channel, the portal app sends a stream request to the server. The server verifies the session, checks the subscription's channel access permissions, and returns a temporary stream URL. This URL is time-limited and tied to the authenticated session, preventing unauthorized sharing of direct stream links. The device's built-in video player (based on the device's hardware decoder) then opens and plays the stream.

VOD content follows a similar flow but includes additional metadata: movie title, year, duration, genre, director, cast, plot summary, and cover art URL. Series content adds season and episode hierarchy. The portal interface presents this metadata in a browsable catalog format, with search and filter capabilities that the middleware's JavaScript application implements client-side.

EPG Integration in Stalker Portal

Stalker Portal handles EPG data server-side. The provider uploads XMLTV-format EPG data to the server, and the middleware processes it into its database. When a device requests EPG information for a channel, the server queries its database and returns the relevant program data as JSON. This server-side approach means the device does not need to download and parse a large XMLTV file, reducing bandwidth usage and improving EPG load times.

The EPG in a Stalker portal supports current/next program display in the channel list, a multi-channel grid view showing several hours of programming across channels, and detailed program information with descriptions and timing. Catch-up TV, when available, is linked to EPG entries: selecting a past program in the guide offers a Play option that fetches the archived stream from the server.

Device Compatibility

Stalker Portal is natively supported by all Infomir MAG devices: the MAG 254, 256, 322, 324, 349, 351, 420, 424, 520, and 524 series. Each MAG model includes the WebKit-based portal browser in its firmware, which connects to Stalker portals without additional software installation.

On Android, STBEmu (and its premium variant STBEmu Pro) emulates the MAG firmware's portal browser, enabling any Android device to connect to Stalker portals. This includes Android phones, tablets, Android TV boxes, and Amazon Fire TV devices. The emulation is thorough enough that the portal experience is virtually indistinguishable from a native MAG device.

Some smart TV platforms have apps that support Stalker portal connections, though compatibility varies by TV manufacturer and model. Samsung and LG smart TVs have third-party IPTV apps in their app stores that support portal URLs, but these apps may not implement the full Stalker protocol, leading to missing features or compatibility issues.

Desktop support is limited. No mainstream desktop application provides full Stalker portal compatibility. Users who want to watch portal-based IPTV on a computer typically use an Android emulator (like BlueStacks) running STBEmu, or use the M3U or Xtream Codes connection method instead, which are supported by desktop players like VLC.

Setup Procedure: Step by Step

The setup process for Stalker Portal connections requires two things: entering the portal URL on your device and registering your device's MAC address with your IPTV provider.

On a MAG device: Power on and connect to your network. Navigate to Settings > Servers > Portals. Enter the portal URL provided by IPTVPlaylist in the Portal 1 URL field. Note the MAC address from the settings screen. Submit this MAC address through your IPTVPlaylist dashboard. Restart the device or select Reload Portal. The portal loads with the full channel lineup.

On STBEmu: Install from the Google Play Store or sideload the APK. Open the app and go to Settings (gear icon) > Profile. Note the virtual MAC address displayed (format: 00:1A:79:XX:XX:XX). Enter the portal URL from IPTVPlaylist in the Portal URL field. Submit the virtual MAC address through your IPTVPlaylist dashboard. Return to the app's main screen and the portal loads automatically.

The MAC address registration step is essential. Without it, the portal URL will respond with an authentication error because the server has no record of your device. Registration typically takes effect within a few minutes. If the portal still does not load after 10 minutes, double-check that the MAC address was entered correctly in your dashboard.

Stalker Portal vs Xtream Codes: Technical Comparison

Both Stalker Portal and Xtream Codes serve the same fundamental purpose: delivering organized IPTV content to player applications. The key technical differences lie in authentication (device-based vs credential-based), interface rendering (server-generated portal vs client-rendered app interface), and client compatibility (narrow vs broad device support).

Stalker Portal delivers the UI from the server, which means the provider controls the visual design and feature set. Xtream Codes delivers raw data, and the client app determines how it is presented. This gives Stalker providers more control but limits users to the portal's design. Xtream Codes users benefit from the diverse interfaces offered by different player apps.

For feature parity, both support live TV, VOD, series, catch-up, and EPG. The practical experience is similar. The choice between them often comes down to device preference: if you have a MAG device or prefer STBEmu's interface, use Stalker Portal. If you prefer TiviMate, IPTV Smarters, or any other dedicated IPTV app, use Xtream Codes.

Common Stalker Portal Issues and Fixes

• Portal loads but shows 'Temporarily Unavailable': The server is under heavy load or undergoing maintenance. Wait 15-30 minutes and try again. If persistent, check with your provider for server status.
• Black screen after portal loading animation: The portal's JavaScript failed to execute. Clear your device's portal cache (MAG: System Settings > Clear Cache; STBEmu: Profile Settings > Clear Cache) and reload.
• Channel list shows but streams do not play: Stream server may be different from the portal server. Check your network connection and verify that your ISP is not blocking the stream server's port.
• EPG data missing or outdated: The provider's EPG source may be experiencing issues. EPG data is managed server-side in Stalker portals, so this requires provider intervention. Wait for the next EPG update cycle.
• Remote control unresponsive in portal: On STBEmu, ensure the app has focus and the on-screen navigation bar is visible. On MAG devices, check remote battery and pairing.

IPTVPlaylist Portal Access

IPTVPlaylist provides Stalker Portal access alongside M3U URL and Xtream Codes API with every subscription. The portal URL and MAC registration are managed through your subscriber dashboard. All 29,500+ live channels, 115,000+ VOD titles, and EPG data are available through the portal interface, with the same content accessible through all three connection methods.

Visit /pricing to select your plan. Browse the channel lineup at /channel-list. For detailed setup guides for MAG, STBEmu, and all other devices, see /setup-guide. Learn about all included features at /features.