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
No worries:
thats not the ea that i was meaning.
if all above happened to me, then, i would be thinking of the possiblity that my trading ea was at fault and causing all the issues. just because it works with no fault on local pc does not guarantee that it will work on a vps.
I agree.
Hence to isolate and prove that point, I migrated a simple EA, that does nothing but firing debug comments: Once on INIT, once every new 15m bar, and every tick.
My hypothesis aligns with your point: if this simple EA works on the local PC and when migrated to the VPS, then it's not the VPS. It's the other EA with 1000+ lines at fault.
Unfortunately, even this simple EA ain't working in the VPS also.
I agree.
Hence to isolate and prove that point, I migrated a simple EA, that does nothing but firing debug comments: Once on INIT, once every new 15m bar, and every tick.
My hypothesis aligns with your point: if this simple EA works on the local PC and when migrated to the VPS, then it's not the VPS. It's the other EA with 1000+ lines at fault.
Unfortunately, even this simple EA ain't working in the VPS also.
what does "custom initialisation log" mean?
does your trading ea require a dll? and how much memory does it use on the vps? how much does it show in use on the vps page?
and since the trading ea is 1000 lines, then, sorry i am out of ideas. even if you did post the ea in its full glory (hahaha), i dont feel motivated to search each line to help isolate the problem.
good luck.
the only other suggestion i have is to run a debug in metaeditor.I agree.
Hence to isolate and prove that point, I migrated a simple EA, that does nothing but firing debug comments: Once on INIT, once every new 15m bar, and every tick.
My hypothesis aligns with your point: if this simple EA works on the local PC and when migrated to the VPS, then it's not the VPS. It's the other EA with 1000+ lines at fault.
Unfortunately, even this simple EA ain't working in the VPS also.