Nexra Studios
Paid ReleasesOverwatch

Installation

Install and start Nexra Overwatch on your FiveM server.

Installation

  1. Ensure ox_lib is installed and started.
  2. Ensure OneSync is enabled on your server.
  3. Place nexra_overwatch in your resources folder.
  4. Add the Overwatch convars from Panel convars to server.cfg.
  5. Add the following to server.cfg:
ensure ox_lib
ensure nexra_overwatch
  1. Restart the server (or start the resource), then open the panel in a browser:
http://YOUR_SERVER_IP:3848

Panel convars

Add this to server.cfg and change the password before going live:

setr overwatch_bind_host "0.0.0.0"
setr overwatch_port "3848"
setr overwatch_trust_proxy "false"
set overwatch_allowed_ips ""
set overwatch_user "admin"
set overwatch_pass "your-strong-password"
setr overwatch_admin_username "admin"
setr overwatch_admin_local_only "true"
setr overwatch_rate_limit_max_attempts "3"
setr overwatch_max_streams "16"
setr overwatch_signal_poll_ms "300"
setr overwatch_default_quality "medium"
setr overwatch_max_viewers_per_target "3"

set overwatch_allowed_ips "" controls who can access the browser panel by IP address.

  • Leave it empty ("") to allow the panel login page from any IP that can reach the panel port.
  • Add a comma-separated list to only allow specific public IPs.
  • Do not add spaces between IPs.
  • Localhost (127.0.0.1) is always allowed.

Example:

set overwatch_allowed_ips "XXX.XXX.XXX.10,XXX.XXX.XXX.25"

With the default overwatch_admin_local_only "true", the built-in admin account can only be used from the VPS itself at:

http://127.0.0.1:3848

Use that local admin session to create staff users, or set overwatch_admin_local_only "false" if you want the built-in admin account available remotely.

Creating staff accounts

The built-in admin account from server.cfg is used to create normal staff logins.

  1. Open the panel from the VPS browser:
http://127.0.0.1:3848
  1. Log in with:
Username: admin
Password: your-strong-password

Use the username from overwatch_user and the password from overwatch_pass if you changed them.

  1. Click Manage Users.
  2. Enter a staff username, password, and max stream count.
  3. Click Create User.

The new staff account can then log in to the panel from an allowed IP. Staff accounts are saved in:

data/users.json

Usernames can use letters, numbers, underscores, and hyphens. The max stream count controls how many players that staff account can watch at once, up to overwatch_max_streams.

Firewall

The panel runs on TCP port 3848 by default. Open that port on your VPS firewall if staff will connect directly.

Linux

Run as root or with sudo:

sudo bash nexra_overwatch/install/linux_setup_firewall_overwatch.sh 3848

Windows

Run Command Prompt as Administrator:

nexra_overwatch\install\windows_setup_firewall_overwatch.bat 3848

If you use a domain with a reverse proxy, keep overwatch_bind_host as 0.0.0.0, set overwatch_trust_proxy "true", and proxy traffic to the configured panel port.

Dependencies

Required

RequirementNotes
ox_libRequired by fxmanifest.lua
OneSyncRequired by fxmanifest.lua
Open TCP panel portDefault 3848, unless the panel is only accessed locally or through a reverse proxy

Auto-detected

Framework bridging is used for character names and player data when available.

IntegrationSupported
Frameworkqbx_core, qb-core, es_extended, custom, or none

For other frameworks, edit framework/custom/.

Locales

Locale files live in locales/. Set Config.Locale in config.lua.

Included: en, de, es, fr, nl, pt-br, tr, cs

Branding

The shipped panel build includes editable branding assets:

FilePurpose
web-site/build/logo.pngBrowser panel logo
web-site/build/theme.cssBrowser panel theme variables

Replace the logo file with your own image, or edit theme.css to adjust the panel theme. The UI source is not required and is not part of the install workflow.

Data files

Overwatch stores panel data as JSON / text files. No SQL install is required.

FilePurpose
data/users.jsonStaff users created from the admin panel
data/blocked_ips.jsonIPs blocked after too many failed login attempts
data/watch_log.txtOptional watch activity log when enabled

Editable files

These remain open for customization (escrow ignore):

  • config.lua
  • locales/*.json
  • server/*.lua
  • framework/**/*.lua
  • shared/map_coords.lua
  • web-site/build/logo.png
  • web-site/build/theme.css

On this page