Tutorial 1-Stream: Adding a Server (Part 2)

[1-Stream]

Once the core server details are established, 1-Stream provides a suite of advanced tools to fine-tune performance, manage global traffic, and secure your infrastructure. This section covers GeoIP balancing, performance caching, and deep-level deployment settings.

---

1. GeoIP Balance Clients​

The GeoIP Balance section (expandable via the +/- buttons) allows for granular control over who can access your server based on their physical location or provider.

• Traffic Control Modes:
  • Off: No geolocation filtering.
  • Prioritize: Directs traffic from specific regions to this server first.
  • Block: Prevents specific countries or IPs from connecting entirely.
• GeoIP LB (Countries): Filter or manually select specific nations from the dropdown list.
• GeoIP LB (ISP): Enables exact load balancing by searching for and selecting specific Internet Service Providers.

---

2. Advanced Performance Settings​

Warning: Recommended defaults are usually best for most setups. Adjust these only if you have specific hardware requirements. Recommended values will display once the installation is complete.

Cache Boost (Persistent Caching)​

To reduce database strain, 1-Stream utilizes Redis and File Caching:

• Redis Caches: Rebuild automatically every 2 minutes.
• File Caches: Require a manual "Rebuild Cache" action.
• Full File Cache: Stores all data for Stalker Portal and Xtream Codes API (with or without episode details) locally.
• LB File Cache (Lookups): Ideal for streaming servers; uses pre-built caches for metadata. You can choose to "Serve when ready" (complete data only) or "Serve even when not ready" (allows partial data during a rebuild).
  

Nginx Caching & Memory Management​

Specific optimizations are available for different device types. Enabling these usually requires a Reconfigure action:

• Targeted Caching: Options available for MAC Devices, Xcode API, XML EPG, and B2C Player API.
• Mount Streams on Memory: Set to YES by default. This uses RAM for stream folders to increase speed. Set to NO only if your server is critically low on RAM.

---

3. Queue & Monitor Workers
​

These workers handle heavy asynchronous tasks. Any changes here require a Restart Services action:

• redis:high: Manages M3U playlist generation and bouquet caching.
• redis:streams / start-streams: Dedicated to FFmpeg health checks.
• redis:transcode: Manages VOD transcoding (FFmpeg).
• redis:default: Handles core security, connections, and stats.
• line-activity:update: Processes real-time user activity updates.

---

4. Advanced Deployment & FPM Settings
​

This section manages PHP-FPM worker processes to ensure the web interface and streaming APIs remain responsive under heavy load.

• LB API Deployment: * For Main Servers: RoadRunner combined with FPM is recommended.
  • For Load Balancers: FPM only for maximum stability.
  • Opcache Preload: Reduces CPU usage but increases RAM consumption.
• Process Management: You can define the Max Children (total workers), Start Servers, and Min/Max Spare Servers for various services including the Panel, LB API, MPEGTS, and VOD.

---

5. Advanced Nginx & Rate Limiting
​

To prevent flooding and DDoS attempts, Nginx uses "Limit Zones." Changes require Manage Servers > Action > Reconfigure.

Zone	Recommended Rate	Purpose
Limit Zone BO	100 r/s	Back Office/Panel requests.
Limit Zone Play	3 r/s	Protects stream-watching links.
Limit Zone Heavy	1 r/s	Limits heavy M3U and EPG requests.
Limit Zone Stalker	20 r/s	Specifically for Stalker portal EPG/M3U.
Limit Zone Sanity	20 r/s	General safety limit for all requests.

---

6. Advanced (Other) & FFMPEG
​

• Management API Domain: Set a specific domain for administrative tasks; defaults to Server Domain if blank.
• Local Streaming IP/Domain: Used exclusively for internal restreams within the service.
• FFMPEG Version: * V4: Best for stability and compatibility with older scripts.
  • V6: Best for updated codecs and modern format support.