Instances - Local instances shows "stopped" when deploy is relaunched

[rapcmia]

Describe the bug

While testing a PR and tried to relaunch deploy by running docker compose restart while there are active instances, it would not recognized the active containers and only display on `stop" status

• Observed only option for a user to stop the bots is either manually execute stop command or use the archive button from dashboard
• This causes our v2 strategy to not be able to close orders on exchange leaving it as active orders

Steps to reproduce bug

1. Setup deploy using docker
2. Select any controller and deploy
3. Launch instance and wait until it successfully place orders
4. Go back to terminal and run docker compose restart

[rapcmia]

not able to reproduced

[rapcmia]

After running couple more tests, issue happened again so reopened 😓

[Nazenator]

Were you able to find a solution for this? I have the same issue.

[cryptropical]

Someone reported to fix this in discord, it seems to be a port conflict. I traced the error back to the backend api not reporting correctly

[Nazenator]

Someone reported to fix this in discord, it seems to be a port conflict. I traced the error back to the backend api not reporting correctly

Ok so how would I resolve the issue?

[rapcmia]

You may want to pull the latest commit from humingbot/deploy and ./setup.sh again. We have added updates with dashboard and hummingbot-api (previously backend-api)

Screen share: https://www.loom.com/share/1f644515a5c14dcea11aa8cdc03fcb1a

[rapcmia]

Linked this issue https://github.com/hummingbot/hummingbot-api/issues/94 since it occured after restart

[Nazenator]

I've pulled the latest commit and setup again but now I can't access the dashboard due an st pages error. See below image: