What should I check when MT5 blocks the reporter's WebRequest?
By Chart Reporter Reviewed 2 min read
The short answer
Check the WebRequest allow-list in Tools → Options → Expert Advisors and add https://api.chartreporter.com exactly as documented. The reporter also needs a valid key and a connected terminal. A local permission error and a server authentication error require different fixes.
Allow the intended destination
MT5 requires you to allow destinations used by an EA's WebRequest calls. For Chart Reporter, use the documented API origin rather than inventing a trade-specific endpoint. Confirm the setting in the terminal instance that actually runs the reporter; a different MT5 installation may have a different configuration.
The reporter installation guide calls out error 4014 as a reason to inspect this setup first. Follow its restart or reattachment guidance after changing permissions. Avoid adding a collection of guessed domains in the hope that one will work. A short, understood allow-list is easier to diagnose and maintain.
Read the error at the right layer
A blocked network function is different from a completed request that receives an authentication failure. In the first case, inspect the terminal's permission and execution environment. In the second, check the response and whether the reporter is using the current Chart Reporter key.
A useful troubleshooting note says what you observed: the exact log message, the time, the terminal version and the EA version. Saying only that sync is broken leaves both permission and authentication possibilities open. Do not include the API key, broker password or a screenshot exposing those fields in a support request.
Confirm the result through existing data
Once the setting is corrected, keep the EA attached and watch for a recent heartbeat in Chart Reporter. Then compare a known record against the account and date filters. This establishes whether the connection works without asking you to trade for the sake of a test.
If the heartbeat resumes but old replay remains missing, do not keep expanding network permissions. Candle history is a separate diagnostic path. Check the broker symbol and requested interval, then use the retry guidance if appropriate. Repeatedly changing unrelated options makes it harder to identify which correction resolved the original problem.
Sources and further reading
Related guides
Why is my MT5 terminal online but my journal looks empty?
Use account, filter, access and trade-state checks to distinguish an empty view from a reporting failure.
What happens to MT5 reporting when I rotate my API key?
Plan a reporter-key rotation across all connected terminals without confusing it with MCP authorisation.