PineHookPineHook

Troubleshooting

Solutions to common issues with PineHook.

Having trouble? This guide covers the most common issues and their solutions.

EA Not Connecting?

PineHook EA shows 'Not connected' or doesn't appear in dashboard

Signals Not Arriving?

TradingView alerts fire but signals don't reach your EA

Trades Not Executing?

Signals arrive but trades fail to execute on MT5

Unexpected Trade Results?

Trades execute but not as expected (wrong size, SL, TP, etc.)

EA Not Connecting?

Try these solutions in order

1
Verify License Key

Check that you've entered the correct license key in EA settings. Copy it directly from your dashboard to avoid typos.

View detailed guide
2
Check Secret Key

If you generated a Secret Key for your license, make sure it's entered in the EA settings. Without it, authentication will fail.

View detailed guide
3
Enable DLL Imports

Go to Tools → Options → Expert Advisors and enable 'Allow DLL imports'. This is required for WebSocket connectivity.

View detailed guide
4
Check Internet Connection

Ensure your MT5 terminal has internet access. Test by opening a browser on the same machine.

Still Need Help?

If you've tried all the solutions above and still experiencing issues, contact our support team at [email protected]. Include your license ID (first 8 characters), error messages, and steps you've already tried.

Quick Diagnostic#

Before diving into specific issues, check these basics:

1. EA Status Check#

In MT5, look at the EA:

  • Blue hat icon in the top-right corner = EA enabled and allowed to trade (grey hat = disabled)
  • No icon = EA not attached or failed to load
  • Check the Experts tab for error messages

2. Dashboard Status#

In your PineHook dashboard:

  • Green "Connected" = EA is online
  • Red "Disconnected" = EA is offline

3. Quick Test#

The dashboard has two built-in testers that are faster than round-tripping through TradingView:

  • Validate Format checks a signal's syntax without sending it ("Signal is valid" or "Invalid signal", with any warnings listed).
  • Test EA Connection sends a round-trip probe to your EA and reports back: "Connection verified" with a "Round-trip OK" badge, plus a trading-permissions check ("All trading permissions OK" vs "Trading permissions issue detected"). If it can't reach the EA you'll see "EA not connected".

Or send a test signal from TradingView and check that it appears in your Signal Logs:

{"license": "YOUR_KEY", "action": "buy", "symbol": "EURUSD", "size_lots": 0.01}

A fired alert is not the same as an accepted signal

A blocked or rate-limited signal can still show as "sent successfully" in TradingView while being stopped on our side. Always confirm the outcome by the status of the row in Signal Logs, not by TradingView's alert log.

Common Issues by Category#

Connection Problems#

EA won't connect to PineHook:

Signal Problems#

Signals not arriving or executing:

Trade Problems#

Trades failing or behaving unexpectedly:

  • Trade Errors - Symbol issues, margin errors, broker rejections

Diagnostic Checklist#

Run through this checklist to identify issues:

CheckHow to VerifyIf Failed
MT5 runningTerminal open and logged inStart MT5
AutoTrading onCheck toolbar buttonEnable it
EA attachedBlue hat icon visible (grey = disabled)Attach EA
DLL imports allowedTools → Options → Expert AdvisorsEnable Allow DLL imports
Internet connectionMT5 shows ping timeCheck network
License validDashboard shows activeCheck subscription

Log Files#

MT5 Experts Log#

View EA output:

  1. Open MT5
  2. View → Toolbox (Ctrl+T)
  3. Click Experts tab
  4. Look for PineHook messages

MT5 Journal#

System-level messages:

  1. View → Toolbox
  2. Click Journal tab
  3. Look for DLL or WebSocket errors

PineHook Dashboard#

  1. Login to dashboard
  2. View Signal Logs
  3. Check for error messages

Reading Signal Logs status#

Every signal in Signal Logs carries a status badge. Which one you see tells you where the problem is and which page to read next:

BadgeMeaningWhere the problem is
EXECExecuted, trade placedNothing to fix
SENTSent to the EA, awaiting confirmationTransient, wait a moment
RECVReceived, not yet forwardedTransient
DLYDQueued (a delay signal waiting to run)Expected
FAILReached the EA but the trade was refusedBroker/EA error, Trade Errors (click the row for the message)
RJCTRejected, the payload failed validationFix the payload, Signals Not Received
BLCKBlocked by a safety gate (symbol filter, active hours, signal auth, or rate limit)Check the block reason on the row
BLKDDuplicate blocked, the same signal arrived twiceExpected, one copy was dropped
ABDNAbandoned, you cleared a queued signalExpected

The key fork: RJCT means fix your payload, BLCK means a setting stopped it, and FAIL means the broker or EA refused a signal that otherwise arrived fine.

Error Message Reference#

Common error messages, what they mean, and where to fix them:

ErrorMeaningSolutionDetails
"Invalid license key"Key not recognizedCheck the key in your dashboardConnection Issues
"Secret key required for this license" / "Invalid secret key"Secret Key set on the license, but the EA's is missing or wrongPaste the Secret Key into InpSecretKeyConnection Issues
"WebSocket error"Connection failedCheck Allow DLL imports is enabledConnection Issues
"Symbol not found"Symbol name doesn't match the brokerSend the broker's exact Market Watch nameTrade Errors
"Trade disabled"AutoTrading offEnable AutoTradingTrade Errors
"Not enough money"Margin too lowReduce lot sizeTrade Errors

Getting Help#

If you can't resolve an issue:

  1. Check the FAQ - Frequently asked questions
  2. Search signal logs - Look for specific error messages
  3. Contact support - Include your error messages and steps tried

Include Details

When contacting support, include: your license ID, error messages, MT5 account type (demo/live), and steps to reproduce.

Next Steps#