02-14-2020, 07:21 PM
(This post was last modified: 02-15-2020, 03:10 PM by trading_gekko2020.)
Im new to Gekko and having this problem when starting the gekko script:
Is it not possible to run behind a Proxy? The Gekko platform starts bu all the exchanges are empty and not possible to edit.
Thanks for any respond to this!
Update: i solved the problem. It seems like it's related to npm functions. When running npm list | grep lodash I get:
│ └── lodash@4.17.15
│ ├── lodash@4.17.15
├── lodash@4.17.15
│ │ └── lodash@4.17.15
│ ├── lodash.get@4.4.2
│ │ │ └── lodash@4.17.15
Then replacing the lodash version by running: npm install lodash@2.x I get:
│ └── lodash@4.17.15
│ ├── lodash@4.17.15
├── lodash@2.4.2
│ │ └── lodash@4.17.15
│ ├── lodash.get@4.4.2
│ │ │ └── lodash@4.17.15
This initates some major errors running: npm audit
found 3 vulnerabilities (1 low, 2 high) in 530 scanned packages
3 vulnerabilities require semver-major dependency updates
The solution is NOT using the command: npm audit fix --force to fix those errors and instead just ignore them.
Then I started up the platform running: node gekko -ui
and things seem to be running smoothly.
Is it not possible to run behind a Proxy? The Gekko platform starts bu all the exchanges are empty and not possible to edit.
Thanks for any respond to this!
Update: i solved the problem. It seems like it's related to npm functions. When running npm list | grep lodash I get:
│ └── lodash@4.17.15
│ ├── lodash@4.17.15
├── lodash@4.17.15
│ │ └── lodash@4.17.15
│ ├── lodash.get@4.4.2
│ │ │ └── lodash@4.17.15
Then replacing the lodash version by running: npm install lodash@2.x I get:
│ └── lodash@4.17.15
│ ├── lodash@4.17.15
├── lodash@2.4.2
│ │ └── lodash@4.17.15
│ ├── lodash.get@4.4.2
│ │ │ └── lodash@4.17.15
This initates some major errors running: npm audit
found 3 vulnerabilities (1 low, 2 high) in 530 scanned packages
3 vulnerabilities require semver-major dependency updates
The solution is NOT using the command: npm audit fix --force to fix those errors and instead just ignore them.
Then I started up the platform running: node gekko -ui
and things seem to be running smoothly.