MQL5 VPS: Community authorization failed and Signal Server disconnected
Before migrating again, confirm that the local Journal shows successful MQL5.community authorization and that real-time signal subscription is enabled.
Then synchronize the VPS again. Changing settings locally after migration does not automatically update the virtual environment until another synchronization is performed.
After migration, check the virtual VPS Journal, not only the local Journal. If authorization still fails after a fresh login and new migration, this probably needs Service Desk because only they can check the server-side authorization.
Make sure you've done everything as described here:
How to Subscribe to a MT5 Signal:
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
My MQL5 VPS subscription ID is 6886640, trading account 251799846, broker server Exness-MT5Real33.
The VPS is started and migration completes successfully. My MQL5.community account (maged77) is successfully logged in on the local MT5 terminal, and “Enable realtime signal subscription” is enabled before migration.
However, the VPS Journal repeatedly shows:
“MQL5.community authorization failed”
and
“signal enabled, not connected to signal server”.
After migration it also reports:
“Gold Reaper New V2 2 subscription found ... disabled” and
“signal subscription disabled, enable realtime subscription in 'Signals' settings”.
The signal subscription itself is active until 12 September 2026. I have already restarted MT5/PC, re-entered my MQL5.community credentials and performed migration several times.
Please check the MQL5.community authorization on VPS 6886640 / signal-server connection from your side