If the portal was installing with manual use and IP server middleware: 192.168.1.1, then NGINX configuration will be:

server{
 
    listen 0.0.0.0:80;
 
    rewrite ^/ch/(.*) /stalker_portal/server/api/chk_tmp_tv_link.php?key=$1 last;
 
    location /stalker_portal {
       internal;
       proxy_set_header Host 192.168.1.1; # <-- Middleware server hostname or IP
       proxy_set_header X-Real-IP $remote_addr;
       proxy_pass http://192.168.1.1:88/stalker_portal; # <-- Middleware server IP
    }
 
    location ~* ^/get/(.*?)/(.*) {
       internal;
 
       set $upstream_uri       $2;
       set $upstream_host      $1;
 
       set $upstream_url http://$upstream_host/$upstream_uri;
 
       proxy_set_header Host $upstream_host;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_pass $upstream_url;
    }
}

Stalker Middleware settings.

In portal configuration (custom.ini) it is neccessary to point server IP address with NGINX in stream_proxy parameter. It is neccessary to setup the option “Temporary HTTP links” in admin interface with TV channel adding. In “Address” field it is neccessary to point the address ffrt http://localhost:8899/udp/239.1.1.1:1234. NGINX must to see udpxy using this address.