Thanks jcl, but I don't believe the VPS is the problem. I have further done the following:

On a completely different computer I have done a fresh install of 1.40.2. I have on this computer run Download on the Z12 account with no problem to verify the install. On this computer running Download on the Z3 account fails as follows (quite different from how 1.34.1 fails, but still failing):

"Login FXCM" prints in the window followed by 2 dots, then nothing. I have waited up to 1 hour to verify nothing further happens. Stop is still available so I click it. Then "!Can't open tables!" and "Can't connect!" are printed. At least this Zorro version doesn't hang completely. diag.txt contains:



Does this help to identify the problem?

Thanks.

My 1.40.0 Z7 demo deployment did not resume trading at the end of the weekend.
I pressed [Stop] then, No, then No, and this seemed to jostle it.

Use the recent version. 1.40.0 was a pre-version with bugs. This is probably not the reason, though. We had been notified by 2 other users that their FXCM connection badly crashed last weekend.

Ddlv: Do I interpret you right that your problem was not Z3, or a certain Zorro folder, but a certain account that does not allow connection anymore since last week?

My Z12 account functions fine from multiple machines via both Zorro (API) and TS.

Since the weekend, my Z3 account does not work from Zorro (API) from at least 2 machines, one with Z3 data, the other without any Z3 .trd or anything else - a fresh install trying Download. However, this account can be accessed fine from TS. The problem is only with Zorro/API.

So, the failure is occurring only on the Z3 account, and only with Zorro (API). Since the failure occurs with multiple strategies, it appears Z3 per se is not the issue. Since the failure occurs on multiple machines, it appears the VPS is not the issue.

FXCM API support is asking to talk to Zorro support directly - what contact should I give them?

Thanks.

Hab auch jedesmal Probleme beim Einloggen. Funktioniert selten auf Anhieb.
Dieses Problem besteht bei jeder Strategy, ob Z3 oder Z12 und auch schon seit einigen Zorro-Versionen.
Ich könnte mir vorstellen, dass nach dem Starten von Zorro, das Passwort-Eingabefeld nicht "empty" ist. Mit anderen Worten, nicht sichtbare Zeichen darin versteckt sind.
Ich hab festgestellt, nach fehlgeschlagenem Logging, Zorro neu zu starten, dann mit Backspace-Taste oder Delete-Taste das Eingabefeld "räumen", dann Passwort eingeben. Dannach funktioniert das Einloggen.
Kann aber reiner Zufall sein.
Zumindest hat es bei mir immer geholfen.

Unsichtbare Zeichen im Eingabefeld verhindern natürlich den Login, das würde sich dann aber in einer Fehlermeldung äußern und nicht im "Aufhängen" der API.

DdlV: give them the op group support address. We had meanwhile reports that several people also experienced a weekend crash of the FXCM API, so something apparently happened with one of their servers. But no one so far had an account that persistently crashes on login.

Is there anything unusual with this account? For instance, single session only, or some particular access restriction?

If nothing helps and the mystery persists, you could continue as follows. Open a new account with FXCM, and transfer all funds from the non-working account to the new account, except for maybe one dollar so that the old account stays open. Then change the password of that account and give us access. We will then debug the login process and can at least provide some info to FXCM what happened, in hope that they can fix it.

The Z3 account is in the Markets part of FXCM and runs on a different server than the Z12 UK account. It is supposed to be multiple access, as I recall, but I don't think that matters?

I will give FXCM the OP Group support email...

Re. giving you access, the account has 2 open Zorro trades - I would have to close them manually, right?

Or, I could give you access to the account now, and then change the password later when the problem is resolved?

Thanks.

Hi jcl & all,

First, thanks to jcl for all the help so far!

For the benefit of others who may come upon this thread, this issue has been escalated to FXCM's developers as a possible bug on their side. They have given no ETA for resolution.

At today's end, it will be 2 WEEKS without API=Zorro access to the account! Initially expecting a quick resolution I just occasionally monitored the open trades through TS, prepared to cancel them if they went too bad. So far they haven't, but of course anything could have happened at a time I wasn't looking. So, this wasn't really an ideal course of action.

jcl, how should a situation of API failure like this be handled? Would the recommended way be to set Stops in TS? At any particular value? In the case of the Z systems, we don't know what stops are in the strategy - only the catastrophic one. When the API began working again, would Zorro automatically update/remove any manually added Stops?

Thanks.

Thank you for your info

It would indeed make sense to manually place stops as long as the account can not be controlled with Zorro. You can see the stops on the status page - take them from the virtual trades, not from the pool trades that have no stops. But I would probably just manually close the trades in such a situation, since it is unclear how long FXCM will need to fix the problem.