Set up
Install the suite, open the ports, finish the first run and keep it backed up.
- InstallationBGPVR runs as a Docker container. The application is stateless — everything that matters lives in the volumes you mount.
- Ports & firewallAlmost everything runs over a single port. Only open what you actually use.
- First runOn first boot the container creates its database, generates a unique security key for your install, and seeds the folder structure under /data .
- Make remote help ready on your serverRemote help on the BGPVR Player app (see a viewer's app screen, press its buttons, change its settings) needs three things from your server. Settings › Clients & privacy › Remote help readiness checks all three through your own web address and shows the command for each red line, filled in for your install. MAG boxes need none of this.
- NVIDIA persistence modeWithout it, the NVIDIA driver shuts a card down whenever no program is using it and starts it again for the next one: each Light recording stream (and the card check before it) then waits about a second longer. Monitor › Technical › Exposed Hardware shows it per card (Persistence mode: On ✓ or Off). It is a setting of the host's NVIDIA driver: the BGPVR container only reads it.
- Public accessSettings → Public access (2.9.352, admin only): the main address viewers use, an optional media address that serves video from a second name, and a check of both from the server. Use a media address when the console sits behind Cloudflare (its terms limit video through its proxy on plans below Enterprise, and its proxy can cut long streams) or behind any proxy that holds video back. Viewers change nothing: the server hands out the new links itself.
- SettingsThe main configuration surface for the install: appearance, public site URL, storage paths, live DVB/transcode tuning, SMTP, health alerting, AI, billing gateways and third-party integrations. Thirteen tabs (General, Tuners & Sources, Conditional Access, Channels & Ordering, API & Security, Forum Sync, Email, Notifications, Clients, AI Processing, Billing, Telegram Integration, and Branding on white-label licences); every card inside a tab has its own Save button and posts only that card's keys.
- ModulesEvery optional module of the suite on one page, switched on or off in one place (2.9.371). The list on the left groups the modules in seven groups (Watching, Apps & protocols, AI, Subscribers & sales, Security & player, Messages & support, Platform & integrations) with search (English and Bulgarian names and words such as MAG, Kodi, 9982, Plex) and filters (All, On, Off, Not in licence, Needs attention); the right side shows the selected module: what it does, its edition, what it needs and what needs it, what is using it now, what happens when you switch it off and what disappears, its own settings and its history. A module that is off or not in your licence disappears from the menu and from every page; only this page keeps it, so you can switch it back on.
- BackupCreate, schedule, download, upload, restore and delete backups. Each backup is a tar.gz with the integrity-checked database, the password key and the session secret. The page also carries the Database maintenance card (retention, housekeeping, compaction).
- Staff AccountsAdmin-only page for delegated access: reusable Permission Profiles, the staff accounts that use them, and the full admin accounts list with two-factor authentication. Three tabs: Permission Profiles, Staff Accounts, Admin Users.