4Trader Gateway

Manager & MT5 terminal watchdog

Developer-only infrastructure. Operators cannot change manager API credentials or LP terminal watchdog behavior from Settings.

Manager (source broker) ? Trade / Omnibus

This is not the LP account. Primary Manager for places, Omnibus, and dashboard when Pump Manager is off.

Server Login Password Certificate password

Pump mode Timeout (ms)

Pump Manager (optional 2nd session)

Off (default): one Manager with Trade before Dashboard priority. On: quotes / position pump use a second Manager login on the same broker (must see the same source groups). Trade/Omnibus stay on the Manager above. Hot toggle does not drop open trades.

Enable Pump Manager

Server Login Password Certificate password

Pump mode Timeout (ms)

MT5 terminal watchdog

Keeps each LP terminal64.exe running under IIS (Session 0). Disable if you manage terminals manually ? do not open duplicate MT5 windows in RDP.

Enable MT5 terminal watchdog Watchdog interval (seconds) How often to verify each LP terminal is still open (15?3600). Default 60.

Destination mode

Developer-only routing. Operators cannot change single vs multiple LP or forward mode from Settings.

Single LP Multiple LPs

Single LP routes to one gateway (current behavior). Multiple LPs fans out each source trade to every enabled target in parallel. Enable LP Poll on a gateway profile to route each open to the best price.

Auto forward Manual forward Mixed forward

Auto: sync all matched source accounts automatically. Manual: display only ? forward from the dashboard by symbol. Mixed: set Auto or Manual per source login or group in Source accounts on the Settings tab.

Enable/Disable Gateway Modules

Disable a module to pause its backend and block dealer portal access. Operator settings are kept. At least one module must stay enabled. Master Dual Copier is off by default.

Track Connect/Disconnect Log

Connect/disconnect events from host and LP gateway diagnostic logs (UTC). Click Refresh to load the latest entries.

Time (UTC)	Source	Event	Reason / detail
Expand this section and click Refresh.

Find Broker Server

Search MT5 broker servers for reference only. Picking a server shows resolved host and port here ? it does not change Settings.

Find broker

Server

Broker server Port(s)

Uses local MT5 servers.dat and remote broker catalog.

Fleet Deploy

Deploy from this development control server to remote gateway targets. Scripts are auto-pushed from dev before each deploy (when missing or stale on remote). Use Sync scripts to update .ps1 files without a full deploy.

	Target	Host	Domain	Ready	Agent	Branch	Commit	Health	Issues / fixes
Fleet deploy not loaded.

Database connectivity

Local primary, dev replica hub, and remote cold-backup DB per fleet target. Probes run from this dev control server.

Target	Local DB	Replica (dev)	Remote backup
?

Deploy log

Setup Host / Server

Dev control server only. Select an existing host to edit, or create a new one. Defaults load from this server?s fleet and backup settings.

Host setup is only available on the dev control server (replicaHub or FleetDeploy:Enabled).

Server identity

Fleet / target ID Display name Group Host label Private host IP Private IP of the new host ? used for MariaDB replication primary and the dev-side AI sidecar URL.

Gateway & deploy agent

Public gateway URL Repo path on host Listen URL (Kestrel) Git branch Build configuration Deploy API key Allowed dev server IPs Comma-separated public/private IPs of this dev control server that may call the deploy API on the new host (DeployAgent:AllowedCallerIps). Only these IPs can trigger git pull + publish remotely. Enabled in fleet deploy list

Local MariaDB

Database name App DB user App DB password MariaDB port

Replication & remote backup

Replicate local DB to dev hub

Dev replica hub IP Replication user Replication password

Push to remote cold backup MySQL

Remote backup host MySQL host for nightly/outbound backup ? taken from this dev server?s config by default; change if your backup DB moves. Remote backup port

Remote backup database name

Remote backup username Remote backup password

Seed local DB from remote on first setup

AI sidecar (optional)

Enable AI sidecar on host Sidecar port Bind host 0.0.0.0 listens on all interfaces so the dev server can reach the sidecar. Use 127.0.0.1 for local-only (dev cannot connect remotely).

Generated setup configs

AI Agent

Chat with a Cursor agent from this dev control server. Pick Dev for commit, push, fleet deploy, and host setup. Pick a remote host to troubleshoot logs and health on that machine.

AI Agent is disabled on this server (AiAgent:Enabled).

Host

Send a message to start. Examples: ?What changed in this repo??, ?Commit with message ? and push?, ?Deploy PFH and Majesty?.

Agent Agent ? can edit, commit, push, and deploy Ctrl+Enter

Troubleshoot ? System ? Manager ? Pump ? Omnibus ? LP

Runs system check (runtime / DB / schema / MT5 DLLs), tests Manager, checks Pump Manager when enabled, probes active Omnibus coverage logins, verifies each MT5 Manager LP trade login (catches Not found (13)), re-probes health pills, and lists UI fixes. Does not create missing MT5 accounts ? fix those under LP Targets or in MT5.

Idle ? click Run fix / diagnose

Response log

Fixes

No run yet

DB Management

Local MySQL tables on this gateway. Export downloads a .sql file to your computer. Import uploads a .sql and can apply structure only or structure + data.

Table	Rows	Data	Index	Total	Engine	Actions
Open this tab to load tables?

Import SQL

SQL file

Structure only Structure + data Dry run (parse only, do not execute)

Field	Meaning
targetId	Short id (letters, numbers, hyphen) ? used in filenames
publicBaseUrl	Gateway domain (no `/4TraderGateway/` path)
repoPath	Git folder on that server
listenUrl	Local port the gateway listens on
apiKey	Leave `""` to auto-generate
allowedDevServerIps	Dev server IP that may trigger deploys

File	Purpose
config/fleet-targets.json	Adds target to fleet list (dev deploy UI)
config/deploy-agent.{id}.json	Config for that server
scripts/setup-deploy-agent-{id}.ps1	One-command installer on target

Sign in

Brand

Configured LP targets

Manager & MT5 terminal watchdog

Destination mode

Enable/Disable Gateway Modules

Track Connect/Disconnect Log

Find Broker Server

Fleet Deploy

Database connectivity

Setup Host / Server

AI Agent

Troubleshoot ? System ? Manager ? Pump ? Omnibus ? LP

Response log

Fixes

DB Management

Import SQL

User popup messages

Sent campaigns

Connection settings

Profiles

New gateway profile

Configured LP targets

New LP target

LP gateway processes

Kanban support requests

Auto dashboard

LP targets

LP positions

Queue (auto forward)

Source positions (live pump)

Auto log (recent)

Manual dashboard

Manual forward

LP accounts (manual trades)

Source positions (manual accounts)

Bonus dashboard

LP accounts (BTH)

Source positions (bonus accounts)

Queue (recent)

Bonus log (recent)

Loss Trailing dashboard

LP accounts (LTH)

Source positions (loss trailing accounts)

Queue (recent)

Trailing queue (pending stops)

Loss Trailing log (recent)

Master Dual Copier

Trade

Open links & events

Master & active groups

Add slave account pair

LOG

Queue (recent)

Recent events

How to add a new server

Step 1 ? Edit the JSON template

Step 2 ? Click Create server files

Step 3 ? Commit & push (so target can git pull)

Step 4 ? On the NEW server (one time)

MT5 connect/disconnect ? full log

Account