Closed xgiovi9810x closed 11 months ago
I don't know if this is the result. Ever since the upgrade to the .key file, I've been unable to build the images from docker-compose up --build. It gives the error. The keys automatically migrate. Even when I put the api key and secret key back in, a rebuild also migrates the keys and the error persists.
@letsautom8, can you help me with the Docker issue please? Seems having a separate .key file is causing issues with Docker. I read in the Telegram chat it may be due to a permission issue.
@xgiovi9810x, is this a persistent issue or did it just happen once?
@whittlem at least for me using Docker, it started once on the update with moving the keys from the config. I haven't been able to get it to work with docker-compose up --build since that update. I believe it was the 2.45.0 update. It doesn't appear to be persistent. I know this is the case with both the coinbasepro and binance keys as I tried both and the errors are similar with the keys.
@whittlem Nope but I didn't do a lot of real time test from that day.
So I'm doing some debug work on the bot (I'm testing a new strategy) and this night it gives me the error in the picture up here; I don't think it is a matter of my own code as I have just replaced the condition in the strategy.py file and more probably this was due to a server error from Binance (but still I think it should be handled without crashing). What do you think?
Note: The bot was running from 20:10 to 4:14 (UTC+2) that it the time when the exception happened