I am experiencing a persistent issue with the built-in AI Assistant in MetaTrader 5.
Try the following client-side troubleshooting:
Forum on trading, automated trading systems and testing trading strategies
AI Assistant MCP in MT5 Beta Build 6194 has no file read tools
Nikolay Safonov, 2026.10.07 09:45
i won... TM5 AI alive! thx DSH for that... here a guide from DSH:1. Confirm it is the endpoint, not your connection
The api2 host answers ICMP but refuses TCP on 80, 443 and 8080: the machine is up, the service is not. The other nodes answer normally:
curl.exe -s -o NUL -w "%{http_code}\n" https://api2.inferdeck.net -> 000 curl.exe -s -o NUL -w "%{http_code}\n" https://api4.inferdeck.net -> 200
If api2 returns 000 and another node returns 200, this is the same problem.
2. Why the Endpoint field cannot be fixed
That value is not yours to keep. With Provider=MQL5.community the endpoint is issued from the MQL5 side and overwrites the local configuration on every start. Tested with the terminal closed:
- closed MT5, set Endpoint=https://api4.inferdeck.net in config\assistant.ini (UTF-16LE), verified the file on disk;
- started MT5;
- 8 seconds later the terminal rewrote the file back to Endpoint=https://api2.inferdeck.net .
So neither a UI edit nor a file edit survives — the same happens with api1 and api3. That matches what others report in this thread.
3. Workaround: keep the name, change where it points
The certificate served by the working nodes is a wildcard: CN=*.inferdeck.net . That means the name api2.inferdeck.net validates fine against any of those nodes. We only need to make that name resolve to a working one.
Find the current address of a working endpoint:
nslookup api4.inferdeck.net
Use whatever your working endpoint resolves to — mine was 203.29.60.35 on 2026.10.07 and may differ for you.
Add one line to C:\Windows\System32\drivers\etc\hosts :
203.29.60.35 api2.inferdeck.net
Steps:
- Run Notepad as administrator.
- Open C:\Windows\System32\drivers\etc\hosts (set the file type filter to "All files").
- Add the line at the very end of the file and save.
- Run ipconfig /flushdns .
- Verify:
curl.exe -s -o NUL -w "%{http_code}\n" https://api2.inferdeck.net It must print 200. Then start MT5 (or restart it if it is already running) and the AI Assistant connects again.
Nothing in the terminal settings is changed — the Endpoint field still says api2, which is exactly what the server wants, so there is nothing to revert.
Note on antivirus
Kaspersky blocks writes to the hosts file even for administrators: an elevated PowerShell script got Access to the path ... is denied with a valid administrator token. Editing the file in Notepad launched as administrator worked, and Kaspersky did not even prompt. If your editor refuses to save, temporarily disable the hosts-file protection in your antivirus, apply the line, then re-enable it.
To undo
Delete the line and run ipconfig /flushdns . Nothing else was modified.
Caveats
- The IP can change over time. If the assistant stops connecting again, re-run nslookup on a working endpoint and update the line.
- Once MQL5 fixes api2, this line will keep sending you to the alternate node. Harmless, but it can be removed then.
- The trick relies on the wildcard certificate. If it is ever replaced with per-host certificates, the redirection would fail TLS validation.
Error message:
503 Service Unavailable – The Inferdeck cluster is temporarily unavailable.
The error message is pretty clear. Error 503 is an answer from the server, just wait some minutes and try again.
All is working as expected currently.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Dear MQL5 Support Team,
I am experiencing a persistent issue with the built-in AI Assistant in MetaTrader 5.
My system details:
Platform: MetaTrader 5, build 6257
Operating System: Windows 10
Provider: MQL5.community
Model: MQL5 Lite
Endpoint: https://api4.inferdeck.net
Error message:
503 Service Unavailable – The Inferdeck cluster is temporarily unavailable.
I have tried restarting MetaTrader 5 and changing the endpoint to https://api1.inferdeck.net. However, after sending a message such as “Hello,” the endpoint automatically changes back to api4.inferdeck.net, and the same 503 error appears.
I also tested the endpoint using PowerShell. The root URL returned HTTP status code 200, but the AI Assistant's chat requests continue to fail with a 503 error.
My MQL5.community account appears to be activated, and MetaTrader 5 reports that I am using the latest version.
Could you please investigate whether this is a server-side issue with the Inferdeck cluster or the MQL5 Lite service? Please advise me on how to resolve this problem.
Thank you for your assistance.
Kind regards,
A MetaTrader 5 user