Ezserver v6.0

Hide the user database behind a service

    Hackers can exploit SSH vulnerabilities to steal user databases, so it's essential to secure SSH access with best practices like key-based authentication and disabling root login. To enhance security, user servers should only be accessible by content servers through strict firewall rules, preventing external access. Users should connect to channel and movie servers, without direct access to user servers. Additionally, distributing user data across multiple servers will help obscure the servers' locations, making it difficult for hackers to compromise the entire system.
    Ezserver v6.0 enables you to distribute users and content across decentralized servers, ensuring robust security for your end users. By leveraging blockchain technology, Ezserver creates a decentralized network that protects user servers from potential hacker attacks, making it more secure and resilient.


v6.0 Screenshots

Dashboard

Users

Channels


Movies

Series

Blockchain Nodes


EPG

User Agent

Middleware (Web View)


v6.0 Specification

Operating System
Windows
All Windows versions
Linux
Ubuntu, Debian, CentOS, Ubuntu 20.04 (rec.)
Channel
Streaming Type
Live
Input Protocol
HTTP / HLS / HTTPS / Adaptive Bitrate
Output Protocol
HTTP / HTTPS / HLS / Adaptive Bitrate
Video/Audio Format
MPEG TS, MPEG 4/H264, H265, ADTS, AAC, MP3
Source Import
M3U Link
Source Link Backup
2 Backup URLs
Video On Demand
Video/Audio Format
MPEG4, AAC, MP3, MKV
Input Protocol
Local Films, HTTP / HTTPS
Output Protocol
HTTP / HTTPS
Source Import
M3U Link
Series
Video/Audio Format
MPEG4, AAC, MP3, MKV
Input Protocol
Local Episodes, HTTP / HTTPS
Output Protocol
HTTP / HTTPS
Source Import
M3U Link
IPTV Panel
Admin Panel
PC Google Chrome
Reseller Panel
PC Google Chrome
Middleware

Minimum Server Requirement

CPU
4v Core
RAM
8 GB
64 GB (recommended)
Storage
160 GB
Bandwidth
1 Gbps unmetered

Study Case #1

  • Set Channel #1 server for master server and other servers connect it to get blockchain information in booting time.

  • User servers are hidden behind Channel #1 server.

  • Players connect Dynamic DNS Server and forward dynamically to one of channel servers.

  • If User #1 server is down, channel servers base blockchain information to get User #2 servers.

  • If Channel #1 server is down, other channel servers base on blockchain information to get user servers.

Study Case #2

  • Set Channel #1 server for master server and other servers connect it to get blockchain information in booting time.

  • User servers are hidden behind Channel #1 server.

  • Players connect Dynamic DNS Server and forward dynamically to one of channel / films servers.

  • If User #1 server is down, other servers base blockchain information to get User #2 servers.

  • If Channel #1 server is down, other servers base on blockchain information to get user servers.

  • If Film #1 server is down, other servers base on blockchain information to get Film #2 server.