Frostybot started failing after ftx.com went down
claudio-silva opened this issue · comments
Apparently, Frostybot is always trying to read market data from FTX, event if the user has no FTX account configured.
So, now that the remote API is no longer available, it fails with an error in exchange.binance.futures.js (for me, at least, as I'm using a Binance account; just to clarify, I am not using an FTX account).
It's no longer possible to trade because of this.
Also, on the developmentbranch, Frostybot keeps throwing errors because it always tries to open a websocket connection to FTX, even if the user has no such account configured.
Thanks for your reply.
Unfortunately, your solution doesn't work.
If I restart the server after running the rm command, it hangs.
I get this output:
useradd: user 'frostybot' already exists
The user `frostybot' is already a member of `sudo'.
Starting Frostybot Server...
Checking for database upgrades
No database upgrade required
And nothing more.
The web server won't start.
same error after rm ftx folder
edit: it want ftx websocket module so i do
cp websocket.deribit.js websocket.ftx.js
and it start again
@Giannizzero I did this, but still not working. Did you perhaps do any other steps?