I’m not sure if this is a bug, but I’ve tried open source Gainium via Docker on Linux Mint and on Windows 11 (via WSL2 using Ubuntu), and I can’t get the paper-trading-1 container to start. I just deleted everything and started over from scratch with a new folder and getting it from github again. I copied the sample .env file and edited it with notepad to add my Coinbase API credentials (I’ve also tried without adding it), and then run docker compose up -d for the first time and here’s a screenshot of the service having an error and saying unhealthy.
We have received your bug report regarding the paper-trading-1 container not starting with Docker. We apologize for the inconvenience and are looking into this issue. We will provide an update shortly.
Probalem could be due to blocked requests from your location to some of exchanges.
I slightly udpated the logic to handle such problems.
I have updated compose file with newer images version. You can try again.
I ran docker compose down to shut everything down, docker compose pull to get new updates, and docker compose up -d to start everything again, but I still get the same unhealthy message for paper-trading-1. Someone mentioned it could be due to my US location though and Binance.com being banned for my IP, where I should be hitting Binance.us instead. I still see the error about symbols.data in the logs for paper-trading. Maybe something didn’t update or redownload though? I’ll start fresh and try again just to be certain.
Oh shoot, I didn’t write down my license key and I can’t request a second one from my subscription, LOL! Can you release that so I can request another and I’ll write it down this time, haha!
Probably related… I don’t see any pairs for a paper coinbase account. I tried PRICEROLE=all and added my coinbase key and secret and restarted, but still no market.
So as I thought the error doesn’t block pairs update process, however due to exchange connector handle 403 errors (and from US location there are plenty of such) it could took a while to finish the process.
I have made an update to remove 403 handler from open source code, since its not actually needed.
You can try to pull latest version of docker compose file. Exchage connetor version already updated.
So far, so good! I was able to create a paper trading account and complete a test demo trade. I saw the list of pairs. Going to create some bots and do more testing, but everything looks good so far.
I’m not sure if this is the place to ask, as it’s a question and not a bug… I’ve got Gainium running as one docker image and n8n running as another docker image. I’d like to automate cloning some bots in the Gainium image. I created an API key and I’m setting up the credential in n8n. It’s using https://api.gainium.io as the base URL, but should it be something else to point to the local instance instead?
