Not all exchanges are available when hosting on heroku

[pasha-shestakov]

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.

I'm submitting a ...
[x] bug report
[ ] question about the decisions made in the repository

Action taken (what you did)
Running gekko on heroku server, without ssl certs or reverse proxy setup.

Expected result (what you hoped would happen)
I expected it to work the same as localhost

Actual result (unexpected outcome)
The only exchanges that are available are: poloniex, kraken, coinfalcon, bitx, and Debug Exchange simulator.
Additionally, i get an error related to websocket, "Websocket is closed before the connection is established".

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

My config.js is an exact copy of the sample config, and my UIconfig.js is as follows.
Liver heroku app here: https://gekkoappapollo.herokuapp.com/#/home

`
const CONFIG = {
headless: true,
api: {
host: '0.0.0.0',
port:
typeof process !== 'undefined' &&
process !== undefined &&
process.env.PORT
? process.env.PORT
: 8080,
timeout: 120000, // 2 minutes
},
ui: {
ssl: true,
host: 'gekkoappapollo.herokuapp.com',
port: '443',
path: '/',
},
adapter: 'sqlite',
};

if (typeof window === 'undefined') module.exports = CONFIG;
else window.CONFIG = CONFIG;
`

[askmike]

Unfortunately that is the case in the current version. We went through a big update and it requires rewritten exchange wrapper files. See here: https://gekko.wizb.it/docs/introduction/supported_exchanges.html

You can run an older version of Gekko (pre 0.6) to have all of them, not really recommended though.

Closing this as it's not a bug. But I am wondering: what exchange did you want to use?

[pasha-shestakov]

@askmike I am not so sure this is the case. For example binance, gdax, bitfinex should all be supported, but none of those appear on the UI, or at api/exchanges.

[askmike]

Ah you are right. Can you try reinstalling gekko broker dependencies? And if there is any error post it there?

[askmike]

Also, please post the output of node gekko --version.

[pasha-shestakov]

Hi mike, thanks for reopening. This is the output of the npm install in exchange dir:

audited 457 packages in 1.831s found 11 vulnerabilities (9 moderate, 2 high) run npm audit fixto fix them, ornpm audit for details

and node gekko --version:

Gekko version: v0.6.3
Nodejs version: v10.7.0

[askmike]

I am not that familiar with Heroku, but are you able to run a node script on there? If so please run: node gekko -c sample-config.js Which will try to start a gekko paper trader over binance (one of the exchanges that is not working for you).

…

On Wed, Aug 1, 2018 at 12:49 PM, Pasha Shestakov ***@***.***> wrote: Hi mike, thanks for reopening. This is the output of the npm install in exchange dir: audited 457 packages in 1.831s found 11 vulnerabilities (9 moderate, 2 high) runnpm audit fixto fix them, ornpm auditfor details and node gekko --version: Gekko version: v0.6.3 Nodejs version: v10.7.0 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2389 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD9rYTslXKxtkCc-Vd1haCoyiFxNPks5uMTNzgaJpZM4VnxRE> .

-- PGP key at keybase.io/mikevanrossum <https://keybase.io/mikevanrossum/key.asc>

[pasha-shestakov]

It runs with no errors, but it is watching poloniex. I believe this was default from the original repo, but i can change it/ make sure its original.

[pasha-shestakov]

I changed config.watch to binance, and this is the output:

`2018-08-01 05:00:01 (INFO): Setting up Gekko in realtime mode
2018-08-01 05:00:01 (INFO):
2018-08-01 05:00:01 (INFO): Setting up:
2018-08-01 05:00:01 (INFO): Candle writer
2018-08-01 05:00:01 (INFO): Store candles in a database
2018-08-01 05:00:01 (INFO):

2018-08-01 05:00:01 (INFO): Setting up:
2018-08-01 05:00:01 (INFO): Trading Advisor
2018-08-01 05:00:01 (INFO): Calculate trading advice
2018-08-01 05:00:02 (INFO): Using the strategy: MACD

Gekko encountered an error and can't continue

Error:

Cannot find module './private-key'

Meta debug info:

Gekko version: v0.6.3
Nodejs version: v10.7.0
`

[askmike]

I believe this was default from the original repo, but i can change it/

make sure its original. This was changed in 0.6.4 (to binance). Note that there have been some stability fixes, though I haven't seen your issue before. Regardless of the issue I would run 0.6.4!

audited 457 packages in 1.831s found 11 vulnerabilities (9 moderate, 2

high) runnpm audit fixto fix them, ornpm auditfor details This is unrelated from your issue at hand.

Cannot find module './private-key'

This comes from a dependency called `sshpk` which is used by request which is used by a number of exchange wrappers. This is definitely related to your dependencies not being installed correctly. I would manually remove them (`rm -rf gekko/exchange/node_modules`) and try to install them again.

…

On Wed, Aug 1, 2018 at 1:01 PM, Pasha Shestakov ***@***.***> wrote: I changed config.watch to binance, and this is the output: `2018-08-01 05:00:01 (INFO): Setting up Gekko in realtime mode 2018-08-01 05:00:01 (INFO): 2018-08-01 05:00:01 (INFO): Setting up: 2018-08-01 05:00:01 (INFO): Candle writer 2018-08-01 05:00:01 (INFO): Store candles in a database 2018-08-01 05:00:01 (INFO): 2018-08-01 05:00:01 (INFO): Setting up: 2018-08-01 05:00:01 (INFO): Trading Advisor 2018-08-01 05:00:01 (INFO): Calculate trading advice 2018-08-01 05:00:02 (INFO): Using the strategy: MACD Gekko encountered an error and can't continue Error: Cannot find module './private-key' Meta debug info: Gekko version: v0.6.3 Nodejs version: v10.7.0 ` — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2389 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD6OBFHzV1Afzl5eUEFYIdGEot9ajks5uMTYggaJpZM4VnxRE> .

-- PGP key at keybase.io/mikevanrossum <https://keybase.io/mikevanrossum/key.asc>

[pasha-shestakov]

@askmike Looks like i have resolved the issue, thanks to your help. For whatever reason, installing node modules with npm didn't work correctly on heroku, so my solution to this was install the node modules locally, and push them to heroku. I removed <node_modules> from the .gitignore, but not <private-*.js/toml> which explains the error that the sample config revealed. Thanks again.

[Jaquedeveloper]

@pasha-shestakov how did you managed to host the app with the ui at Heroku? I can only have the app there running without the ui and have no access to the API... I am working on writing another UI, so I don't really need access to this UI but I need to have access to the API data and seems like I can't without the UI. What did you do to make it work? Thanks in advance and congrats, I am doing research for a while and some devs here tried and seems that you are the only one who succeeded with it... I've tried to combine info from here, #758 and #338. No success, though...

[pasha-shestakov]

@Jaquedeveloper Hi, I don't remember the specifics as this was quite awhile ago. Getting it working on Heroku was standard, other than dealing the npm dependencies yourself. If you don't need the UI, you can use the gekko server api?