Fix PineHook MT5 EA and cTrader connection errors, including missing DLL permissions, invalid credentials, expired authorization, and repeated disconnects.

When your account will not connect or keeps disconnecting, the status beside its license helps identify where to start. Follow the checks for cTrader or MT5 below. If the license already shows Connected but a trade fails, open its error in Signal Logs to investigate execution.

cTrader connection issues#

License status or symptom	Fix
No account linked	Open the license's three-dot menu and choose Manage broker account, then select an account and click Link account. If no account is available, use Connect another account to authorize one through cTrader.
Reconnect needed	Open Settings → Platform connections, click Reconnect, and authorize the cTrader ID again.
No accounts after authorization	Repeat authorization, making sure to select your trading accounts on cTrader's page. If it opens under the wrong cTrader ID, sign out there and sign in with the ID that owns the broker account.
Linked, waiting for service	Wait briefly for the connection to complete, then refresh Licenses. If the same status remains, check service status before reconnecting the cTrader ID.

While cTrader authorization is unavailable, PineHook cannot submit closes or cancellations to that account. If you need to repeat the setup, Connect cTrader walks through authorization and account linking.

MT5 EA connection issues#

On the MT5 terminal running PineHook, open View → Toolbox → Experts and find the connection error. Use its wording to choose the checks below, whether that terminal runs on your computer or a VPS.

WebSocket connection failed#

Check that the DLL is installed with the EA and still named exactly PineHook.dll, since renaming it prevents the EA from loading the expected library. See Connect MetaTrader 5 for the required file locations.
Enable Allow DLL imports on the Experts tab of Tools → Options (Expert Advisors in older builds), then check DLL permission in the EA's Dependencies tab and restart the EA.
If the error persists, confirm the computer has internet access and check service status. If both are working, review any firewall or proxy restriction on outbound connections to relay.pinehook.io on port 443.

PineHook connects through its DLL, so adding a WebRequest URL to MT5's allowlist will not resolve this error. Allow DLL imports in MT5 covers the DLL settings and file checks in detail. Algorithmic trading permissions control order execution separately, as explained under Trade disabled.

Invalid license key#

In Dashboard → Licenses, confirm that the license is assigned to MT5 and has not been deleted, then copy its current key into the EA's License Key input. Remove any extra spaces before reconnecting.

An inactive subscription can leave the license connected in close-only mode while blocking new trades, so it does not explain an invalid-key error. Read the reported restriction before changing the connection settings.

Secret key required for this license / Invalid secret key#

Enter the matching key in the EA's Secret Key input and reconnect. If you lost it, generate a replacement through Set Secret Key in the license's three-dot menu, then copy the value while it is displayed and update the EA. The dashboard cannot show an existing key again.

Because a new key is checked when the EA connects, an instance already online can remain connected until its next reconnect. Reconnect after updating the input to confirm that the replacement works, and keep the Secret Key in the EA rather than in a TradingView alert.

Already connected / a chart disconnects itself#

One PineHook chart handles every supported symbol on the MT5 account, so remove any extra PineHook instances using the same license. A second connection takes over from the first and can cause repeated disconnects if both remain active. For a separate trading account, use a separate license.

SSL certificate error#

Check the computer's date and time, then install Windows updates and update MT5 so the terminal has current certificate support. If TLS errors continue, check whether a corporate proxy or security application is intercepting the connection and share the exact error with support.

Connection timeout#

After checking internet access and service status, restart MT5 to try a fresh connection. If PineHook alone still cannot connect, try another network to see whether a local restriction is involved, then review outbound port 443 with your network administrator.

Reconnection behavior#

MT5 reconnects automatically after a connection drops, with retry behavior suited to the selected Connection Profile. Choose VPS for an always-on server or LOCAL for a home computer or Wi-Fi connection.

Once the platform reconnects, your Missed alert recovery mode and Recovery expiry determine what happens to queued alerts. Notify Only does not execute them automatically, while Closures Only recovers eligible closes and cancels within the selected window. Expired alerts are not recovered, and alerts rejected by validation or trading rules are not retried. See Missed alert recovery for the differences between MT5 and cTrader, and MT5 EA disconnected for why entries are never replayed late.

Position mismatch alerts#

After you change a position manually, MT5 may show a one-time Position mismatch or Volume mismatch notice while PineHook updates its expected position to match the terminal. You do not need to acknowledge that notice, but if new ones keep appearing, check for repeated manual changes, connection interruptions, or broker adjustments and share the logs with support.

Still having issues?#

If the connection still fails, ask the Support Chatbot for help or to open a ticket, including the license ID, platform, exact error, and checks you tried. For MT5, include the EA and DLL versions as well, but remove Secret Keys and broker passwords from anything you share.

Connection Issues