HonorPro Hub · Broker Onboarding

Plugin Installation Guide

Installing your entitled plugins on the MetaTrader 5 server, and wiring them to the gateway — safely, inside a restart window you control.

1 · Where plugins come from

Your hub cabinet → Downloads lists every package your license entitles you to. Each download card shows the SHA-256 of the file; the Hub Agent verifies the provider's Ed25519 signature automatically for agent-delivered artifacts — for manual installs, compare the hash after download:

certutil -hashfile copyengine.zip SHA256      # Windows
sha256sum copyengine.zip                       # Linux

Locked entries in Downloads mean the feature is not in your plan — the file is not served, and installing a copy obtained elsewhere will not activate it: every plugin independently verifies your signed license.

2 · Installing an MT5 server plugin

Plugins are native 64-bit DLLs loaded by the MT5 server process. Installation always follows the same shape:

Pick a restart window. Loading a new plugin requires an MT5 server restart. Plan it like any trading-infrastructure maintenance: outside session hours, with your LPs notified if needed.
Copy the DLL from the downloaded package into the server's plugin folder:
```
C:\MetaTrader 5 Platform\Server\Plugins\
```
Place the plugin's config (if the package contains one) next to it, or in the folder named in the package's README. Tokens inside configs are yours to set — use fresh random values.
Restart the MT5 server inside your window. In the server log, confirm the plugin reports loaded.
Verify from the gateway: admin console → Settings → Plugin Connections → the plugin's row → Test. A green Connected badge with a latency proves the whole path.

3 · Wiring: tunnels and tokens

Plugins listen on loopback of the MT5 server — they are never exposed to the internet. The gateway reaches them over an SSH tunnel from the Ubuntu box:

# /etc/systemd/system/mt5-bridge-tunnel.service (example)
[Unit]
Description=SSH tunnel to the MT5 Server API bridge
After=network.target
[Service]
ExecStart=/usr/bin/ssh -N -o ServerAliveInterval=30 -o ExitOnForwardFailure=yes \
    -L 127.0.0.1:18091:127.0.0.1:8091 mt5tunnel@YOUR-MT5-SERVER
Restart=always
[Install]
WantedBy=multi-user.target

Plugin	Conventional local port	Gateway setting
Server API bridge	127.0.0.1:18091	`BRIDGE_URL` + `BRIDGE_TOKEN`
Copy-trading engine	127.0.0.1:18092	`COPY_URL` + `COPY_TOKEN`
Additional plugins	18093+	add in Settings → Plugin Connections

Every connection can be added, edited, tested and toggled in the admin console — Settings → Plugin Connections. Edits apply live and are audited.

4 · Activation is the license, not the file

The Hub Agent keeps a signed license on your gateway; each plugin and the gateway verify it independently. Expiry has a 72-hour offline grace window.
What you enable in the cabinet's Feature Store is what actually serves — a plugin whose feature is switched off stays dormant even when installed.
Upgrades: new versions appear in Downloads; agent-delivered updates are staged automatically and installed in your next restart window.

Something not connecting? The order to check: plugin loaded in the MT5 server log → tunnel service active on the Ubuntu box → Plugin Connections badge (Auth failed means token mismatch; Unreachable means tunnel/port) → license state on the cabinet Dashboard.

HonorPro Hub · Plugin Installation Guide · 2026-08-20