❌ EA Not Receiving Signals

• ✓ Is Nexus Server running? Check for the console window. Try visiting http://127.0.0.1:5000/get_trade in a browser.
• ✓ Does the Server URL in EA parameters match the actual port? Default: http://127.0.0.1:5000/get_trade
• ✓ Is Telegram connected? Check for a green connected status in the Configurator's Telegram tab.
• ✓ Is the channel added and enabled in the Configurator?
• ✓ Are WebRequests allowed in MT5 for http://127.0.0.1:5000?
• ✓ Check the EA log file in MT5 Data Folder → MQL5/Files/ for error messages.

❌ Orders Not Opening

• ✓ Does the symbol exist in your broker's MT5? Check Market Watch. Add a Symbol Mapping if needed.
• ✓ Is Symbol Filter active and blocking this symbol?
• ✓ Is Time Filter active and outside allowed hours?
• ✓ Has Max Simultaneous Trades limit been reached?
• ✓ Is Drawdown Protection triggered (trading stopped for the day)?
• ✓ Is the license valid? Check EA log for license errors.
• ✓ Is AutoTrading enabled in MT5 (the green robot icon in the toolbar)?

❌ Signals Without Symbol Not Working

• ✓ Is "Force Symbol If Missing" enabled in BOTH the Configurator (Symbol Mapping tab) AND the EA inputs?
• ✓ Does "Symbol to Force" exactly match the broker's symbol name (including any suffix like 'm' or prefix)?
• ✓ Check the EA log for entries containing "symbol_forced" to confirm the feature is triggering.
• ✓ Check Nexus Server log for the parsed signal to see if symbol_forced = true in the JSON response.

⚠️ A Channel Message Did Not Open a Trade (By Design)

Since July 2026 Nexus is better at telling a real order apart from a message that merely talks about trading. The cases below are ignored deliberately, and each rejection now states its reason in the log.

• 🚫 Results of already-closed trades. "Our BUY EURUSD 1.0850 SL 1.0800 TP 1.0900 was closed manually" repeats the original prices, but the trade is over. It used to be re-opened; not any more.
• 🚫 Plans and conditionals. "If gold breaks 2400 we buy" states an intention, not an order. Ignored unless the message carries an explicit entry (@ price, ENTRY:, BUY LIMIT).
• ✅ "no SL" no longer clears your stops. Inside a new signal, "no sl" means "this trade has no stop", not "remove the SL from my open positions".
• ✅ Mixed messages. When one message carries both a command and a new signal, both are now processed; the signal used to be lost.
• 💡 If you believe a legitimate signal was discarded, send us the exact message — we add it to our regression test suite.

❌ Pre-Signals Not Being Detected

• ✓ Is Pre-Signal Enabled = true in the EA inputs?
• ✓ Is the phrase template configured in the Configurator's channel settings (not just globally)?
• ✓ Does the template match the actual message format? Templates are case-insensitive but must match the structure.
• ✓ Check Nexus Server log for "pre-signal" parsing entries to see if the message reaches the parser.
• ✓ Note: parentheses in templates are valid and properly escaped internally.

❌ License Error

• ✓ Verify the License Key is entered in BOTH the EA inputs and the Configurator's License tab.
• ✓ Confirm the license is registered for your current MT5 account number.
• ✓ Check internet connection — the license requires online validation on startup.
• ✓ If you changed brokers or account numbers, contact support to transfer your license.

❌ Nexus Server Won't Start or Connect

• ✓ Run Nexus Server.exe as Administrator (right-click → Run as administrator).
• ✓ Check Windows Firewall — add an inbound rule to allow port 5000.
• ✓ Check if another process is using port 5000: run netstat -an | findstr 5000 in Command Prompt.
• ✓ Check antivirus — add Nexus Server.exe to the exclusions list.
• ✓ Ensure .NET 8 Runtime is installed (check the installer or download from Microsoft).