App servers IP's and getting client's IP, fix for black screen on live video, time shift, recording and archive.

important message: 

This article is meant for the IPTV Provider (or Portal admin) to do to make sure their Portal settings are correct for our app.

We can help your IPTV Provider (or Portal admin) to get the settings right (on best effort basis) however making those changes is entirely up to the Provider.

A capable system administrator can easily perform all the steps below however not all Portal admins have the needed (root) access (to the Portal servers). Also Portal resellers have limited access.

We have no access or control over any Portals or streams and we do not provide any streaming services!


Dear Service Providers,

In order to guarantee smooth service and avoid compatibility problems we recommend you white list (or unlock in case of blocked) our Server IP's in your Panels, Streaming Servers and Billing Servers.

The application works by connecting to your portal thru our app servers.
So app users may appear connecting to the Portal from our app servers's IP (depending on region and availability, see the IP's below)
This is wrong, please see below for solution and correct way to get client's public IP!

Smart TV's access any streaming links directly (from the TV's Public IP address, we never proxy any streaming traffic!).

Please make sure you "read" the Public IP address of each TV by reading "X-Forwarded-For" headers coming from our app users.
This way you will always have the Smart TV's public IP address and make the app compatible with your Portal.
Some popular middleware solutions are  doing this automatically.

Doing this is strongly recommended, it will fix possible black screen problems with your portals too.
Please do not forget to do this on all your Portal servers, streaming servers, time shift servers, recording (npvr), archive and catchup servers, billing servers and everything associated with your service. 
Otherwise, for example, if you don't do it on your Time shift/recording servers, then Time shift  may not work for the Smart STB users.
Other example case: app may not remember the username and password if it's blocked on the authentication server but not blocked on the Portal.

Properly unblocking the app for your IPTV service will fix the "Portal may be having problems" message.

Our current list of app IP's is :

Australia (
Brazil 2, South America (
Balkans test (
Bulgaria (
Bulgaria (
Canada (
Canada (
France - Bourgeoisie (
India (
Italy (
Luxembourg + Russia (
Rest of the world + Asia (Wide) (
Romania (
Singapore + Oceania (
South Africa + Lesotho (
Spain + Portugal HA (
UK3 + Ireland (
UK4 + Ireland (
Ukraine (
USA (HA-Backup) (
USA (East) + North Continental Americas (
USA (West) + South Continental Americas (
World Web and Portal Validator #1 (
World Web and Portal Validator #2 (
World Web and Portal Validator #3 (

Click here for an NGINX sample config containing all of the IP's above.

IP's listed above are for international app delivery and can change.  There are possible regional or local servers in certain areas that may not be listed here. Read below for them.
In case of local network delivery: Local IP's like are used in cases where IPTV and app delivery is done in a Local Area Network inside your local ISP. Local VLAN ID for Smart STB is 155 or whatever is used for IPTV delivery unless stated otherwise in your corporate activation email.

One good way to tell what server IP is used by the client is to ask them to press any number key on the Remote during "Loading Portal" - they will get similar screen:

In this example [] is the local server's name and [] the IP address.

In case you use Apache2 configuration, you do not need to do anything special, default configuration should give you the correct Client IP's

  1. <VirtualHost *:88>
  2. ServerAdmin webmaster@localhost
  3. DocumentRoot /var/www
  4. <Directory /var/www/stalker_portal/>
  5. Options -Indexes -MultiViews
  6. AllowOverride ALL
  7. Require all granted
  8. </Directory>
  9. ErrorLog ${APACHE_LOG_DIR}/error.log
  10. CustomLog ${APACHE_LOG_DIR}/access.log combined
  11. </VirtualHost>

In case you use nginx or other similar solution, we advise you to add those options to your nginx configuration for your Portals, Streaming Servers and Billing Servers to guarantee app compatibility and correct client IP's visible to you at all times.

  2. server {
  3.     listen       80;
  4.     server_name  localhost;
  6.     location / {
  7.         proxy_pass;
  8.         proxy_set_header Host $host:$server_port;
  9.         proxy_set_header X-Real-IP $remote_addr;
  10. ###proxy smart stb
  11. set_real_ip_from;
  12. set_real_ip_from;
  13. set_real_ip_from;
  14. ...
  15.     }
  17.     location ~* \.(htm|html|jpeg|jpg|gif|png|css|js)$ {
  18.         root /var/www;
  19.         expires 30d;
  20.     }
  21. }

One good way to check if the client's IP you see is correct is to login to your Panel and see the user's info. If the IP is like our app server IP's then the configuration is wrong. If the IP address you see is the same as the public IP address of your client, then everything is okay.

In this example clients with Virtual MAC 00:1A:79:95:9E:95 and 00:1A:79:01:02:03 have WRONG login and their actual Public IP is not visible.
This can cause black screen problems for the example clients.

Individual guides for other most popular middleware platforms is coming soon, examples above are for Ministra.

  • 88 Users Found This Useful
Was this answer helpful?

Related Articles

OperatorCP has been moved - how to login and use new OperatorCP

Dear corporate clients, OperatorCP has been moved to our new website.   How to login and use...

API version 2 for Providers

Please note: this part is technical (for advanced users only) which describes how you can use our...