MT5 Build 6308 – EA Unable to Send Telegram Notifications

My friend developed an Expert Advisor (EA) that sends notifications to Telegram. However, after installing it on a new VPS, the EA was no longer able to send notifications, while it continued to work normally on the previous VPS.

After investigating the issue, I noticed that the two VPS instances were running different MT5 builds.

Issue identified:

  • MT5 Build 6308: The EA is unable to send notifications to Telegram (Error 1009)

  • MT5 Build 6230: The EA works normally and successfully sends notifications to Telegram.

I tested downgrading MT5 from Build 6308 to Build 6230, and the EA immediately resumed working as expected.

This suggests that the issue may be related to changes introduced in MT5 Build 6308.

I hope this information will help your technical support and development teams investigate and resolve the issue in a future update.

Thank you for your attention.

Best regards,

The issue cannot be reproduced in 6305/6309. The message was successfully sent to the channel. Please check your terminal and EA settings.

  1. Configure MetaTrader 5 (MT5) WebRequest:
    • Open MT5 and go to Tools -> Options -> Expert Advisors .
    • Check the box for "Allow WebRequest for listed URL" .
    • Add https://api.telegram.org to the allowed URL list.
Bots: An introduction for developers
  • core.telegram.org
Bots are small applications that run entirely within the Telegram app.
Sergey El #:

The issue cannot be reproduced in 6305/6309. The message was successfully sent to the channel. Please check your terminal and EA settings.

  1. Configure MetaTrader 5 (MT5) WebRequest:
    • Open MT5 and go to Tools -> Options -> Expert Advisors .
    • Check the box for "Allow WebRequest for listed URL" .
    • Add https://api.telegram.org to the allowed URL list.
I already added it during testing...

But I forgot to mention that it's running on Windows Server 2012 R2

Try checking webrequest.

PowerShell

# Force TLS 1.2 for the current PowerShell session
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

# Send the web request using basic parsing (bypasses Internet Explorer engine dependency)
$url = "https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getMe"
$response = Invoke-WebRequest -Uri $url -UseBasicParsing

# Display status and response body
$response.StatusCode
$response.Content

or

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

try {
    $response = Invoke-WebRequest -Uri "https://api.telegram.org" -UseBasicParsing -ErrorAction Stop
    Write-Host "Connection successful! Status code: $($response.StatusCode)" -ForegroundColor Green
} catch {
    if ($_.Exception.Response) {
        $statusCode = [int]$_.Exception.Response.StatusCode
        Write-Host "Server reached successfully! HTTP Status Code: $statusCode" -ForegroundColor Green
    } else {
        Write-Host "Connection failed: $($_.Exception.Message)" -ForegroundColor Red
    }
}

Bots: An introduction for developers
  • core.telegram.org
Bots are small applications that run entirely within the Telegram app.
Reproduced and reported to MetaQuotes.
Alain Verleyen #:
Reproduced and reported to MetaQuotes.
I think the issue is related to TLS 1.2 because I tested MT5 build 6308 on Windows Server 2022, and it worked fine.

The issue only occurs on older Windows versions, such as Windows Server 2012 R2.

Forum on trading, automated trading systems and testing trading strategies

MQL5 VPS synchronization fails – Error 1009 (TLS certificate verify failed, -188)

Sergey El, 2026.11.12 14:19

Please complete the following steps and check whether the issue persists:

  1. Update Windows: Install the latest available Windows updates and restart your computer.
  2. Update MetaTrader: Update your MetaTrader terminal to build 6314 or newer, then restart the terminal.