Do you need the relay at all?
Two of the copiers never use a website. Tick what is true for you.
https:// address without opening your router. Key = a password for one terminal.You never need an account to use a PFX tool. The two that use the internet, the PFX Executor and copying between computers, talk to a small program called the relay. You can run that relay yourself, on your own PC or VPS. It is free, it makes its keys on your machine, and it never contacts PrecisionFX.
The relay places no trades. Your EAs do, under their own settings, and the copy follower does nothing until you switch it on in two places. If a step doesn't look like the picture, that's normal: open the "Not seeing it?" box under it.
Two of the copiers never use a website. Tick what is true for you.
https:// address without opening your router. Key = a password for one terminal.One zip. Everything is inside.
C:\PFX-Relay.| Download | For |
|---|---|
| PFX-SelfHost-Relay-Windows.zip ↓ | Windows PC or VPS. Node.js is already inside, nothing to install. |
| PFX-SelfHost-Relay-Linux.zip ↓ | Linux, macOS or Docker. Needs Node.js 20 or newer. |
SELF-HOST-GUIDE.html, and the PFX Copy EAs in its EAs folder.The download is big. The Windows zip carries Node.js, the program that runs the relay, so there is nothing else to install. The Linux zip is small.
Double-click, then leave the window open.
START-RELAY.cmd.First run: made relay-config.txt with new keys, made on this computer.Windows protected your PC Press More info, then Run anyway. Or unblock the zip first (step 1) and unzip it again.
Port 8787 is already in use The relay is already running in another window. Use that one, or change port in relay-config.txt.
Node.js was not found You have the Linux download on Windows. Get the Windows zip.
relay-config.txt. Keep it private: the keys are passwords.
relay-config.txt in Notepad. Every line is name = value.new where the key goes and save. To stop a key, delete its line.| Line | What it is |
|---|---|
webhook = pfxr_... | A TradingView webhook address |
terminal = pfxk_... | The key for one PFX Executor |
copy_source = pfxcopy_... | The key for the PFX Copy Source EA (the account you trade) |
copy_follower = pfxcopy_... mode=off | The key for one Follower EA. mode=off watches only. mode=on copies new trades |
Settings: line 7: ... The window says which line is wrong and why. Fix that line and save. Nothing else stops.
TradingView and the copy EAs need a safe https:// address. A tunnel gives one.
cloudflared-windows-amd64.exe from Cloudflare's cloudflared downloads, rename it cloudflared.exe, put it in the kit folder, set tunnel = quick and restart the relay.Relay address for every EA.| Option | How |
|---|---|
| Quick test | tunnel = quick. The address changes every restart, so use it for testing only. |
| Cloudflare Tunnel (recommended) | In Cloudflare Zero Trust, Networks › Tunnels, create a tunnel and copy its token. Add a public hostname such as relay.yourdomain.com pointing to http://localhost:8787. Then set tunnel = cloudflare, cloudflare_token and public_address. |
| ngrok | Run ngrok http 8787 --url=https://your-name.ngrok-free.app in its own window and set public_address to that address. |
listen = 127.0.0.1). The tunnel reaches it from inside. You never open a port on your router.Could not start cloudflared.exe cloudflared.exe is not in the kit folder, or still has its long download name.
The tunnel stopped Check the internet connection, then restart the relay.
Once per terminal.
In MT5, allow WebRequest for.WebRequest is not allowed for The Executor says this until the address is on the list. Add it exactly as printed.
MT5 is blocking the relay address. The PFX Copy EAs say this. Same fix.
TradingView alerts into MT5, through your own relay.
TradingView webhook address into your alert's Webhook URL. The alert message does not change.queued as #1, then collected #1, then what the EA did.| Input | Set it to |
|---|---|
| Signal source | PrecisionFX Cloud |
| Cloud: terminal key | your terminal = pfxk_... key |
| Cloud: relay address | your address, for example https://relay.yourdomain.com |
terminal key rejected The key in the EA does not match a terminal line. Copy it again.
The window says the alert came to an address that is not in relay-config.txt. The webhook URL in TradingView is old or mistyped. Copy it from the window again.
It skipped entry alerts older than 10 minutes. The terminal was off. Old entries are never traded late; closes still go through.
The PFX Copy EAs from the kit's EAs folder. Start on demo.
Copy EAs address the window printed. Key = your copy_source key.mode=on in relay-config.txt, and tick Allow this EA to place orders in the Follower EA.The relay address must start with https:// Use the tunnel address from step 4, not http://127.0.0.1.
The relay does not recognise this key. The key is not in relay-config.txt, or its line was deleted. Copy it again.
This key is bound to a different account. Each key belongs to one account. To move it, write new in place of the key and paste the new key into the EA.
The relay makes every key with your computer's own random generator and never sends it anywhere.
No account, no check-in, no updates. The only outside connection is the tunnel you switch on.
Unless you change listen. The tunnel reaches it from inside, with no open router port.
Copies and trades keep their stop loss and take profit. They are just not managed until the relay runs again.
Risk warning: The relay passes your own alerts and trades between your own terminals. Trading carries a high risk of loss and is not suitable for everyone. Copying repeats losses as well as profits. MetaTrader and MQL5 are trademarks of MetaQuotes Ltd.; PrecisionFX is not affiliated with or endorsed by MetaQuotes.