MT5 Signal Integration Issue – VM Service Crash on Port 9090

New comment
 
Hi all,

I’m running into an issue with my MT5 integration and wanted to see if anyone has dealt with something similar.

The Issue in Simple Terms:
My trading platform (on an OpenSUSE staging server) is generating signals correctly (e.g., BTC at 69% confidence). The problem is those signals aren’t reaching the MT5 terminal because the bridge service inside my Windows VM stopped responding.

Architecture Overview:

Trading Platform (OpenSUSE staging server) → generates signals

Network Connection → confirmed working (ping OK)

Windows VM (VirtualBox, 192.168.33.60) → runs simple_vm_server.py to push signals into MT5


What’s Working:

Signal generation ✅

Network connectivity ✅

Fallback detection ✅


What’s Broken:

The VM service (simple_vm_server.py) crashed and stopped listening on port 9090 ❌


Timeline:

Until 15:02 → signals transmitted successfully

~15:06 → VM service stopped responding (likely crash)

After that → platform retries → fails → retries → fails → gives up


Current Technical State:
From the staging server I can ping the VM fine, but nothing responds on port 9090. It’s like calling a number where the line connects but nobody picks up.

Solution So Far:
Restarting simple_vm_server.py on the VM resolves the issue immediately, and queued signals flow straight into MT5.

Question for the Community:
Has anyone else experienced stability issues with a Python-based bridge into MT5? Would you recommend:

1. Running the script under a process manager (systemd, NSSM, Supervisor) for auto-restart, or


2. Moving to a different approach (direct sockets in MT5 or another integration layer)?



Thanks,
Ben
 
Benjamin Banks:

Running the Python bridge under a process manager so it auto-restarts will stop the outages, even if it doesn't fix the root cause yet.

Enable logging and a simple health check on port 9090 to see why it dies. If crashes keep happening, then consider moving the socket handling into MT5 or another robust layer.

In most setups, auto-restart plus logs is enough to keep things stable.

 
Miguel Angel Vico Alba #:

Running the Python bridge under a process manager so it auto-restarts will stop the outages, even if it doesn't fix the root cause yet.

Enable logging and a simple health check on port 9090 to see why it dies. If crashes keep happening, then consider moving the socket handling into MT5 or another robust layer.

In most setups, auto-restart plus logs is enough to keep things stable.

Thanks for the suggestion Miguel. I look into that today. 

New comment