Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker container repeatedly crashing and not restarting #13

Closed
bruzska opened this issue Nov 20, 2021 · 4 comments
Closed

Docker container repeatedly crashing and not restarting #13

bruzska opened this issue Nov 20, 2021 · 4 comments

Comments

@bruzska
Copy link

bruzska commented Nov 20, 2021

Hey after using your awesome project for a little while without issue, the proxy is now repeatedly crashing and not restarting regardless of the docker restart policy. The only error I've been able to find is:

FATA[0185] Error: %sread tcp 172.18.0.2:52570->99.84.133.34:443: read: connection reset by peer caller="/src/proxy/kucoin/kucoin.go:135 (*ws).serveFor" stack="/src/proxy/kucoin/kucoin.go:135 (*ws).serveFor\n/usr/local/go/src/runtime/asm_amd64.s:1581 goexit"

Let me know if there's any other info I can provide to help get to the bottom of this.

@mikekonan
Copy link
Owner

Could you show your docker-compose.yml?

@bruzska
Copy link
Author

bruzska commented Nov 20, 2021

Could you show your docker-compose.yml?

freqtrade-proxy:
    image: mikekonan/freqtrade-proxy:main
    restart: on-failure
    container_name: freqtrade-proxy   

The proxy is crashing after only a few minutes at the moment so I'm worried the issue may be bigger than simply a container not restarting.

@mikekonan
Copy link
Owner

about the restart policy - https://docs.docker.com/compose/compose-file/compose-file-v3/#restart_policy.

this error is about connection has been lost. How are you running the proxy?

@bruzska
Copy link
Author

bruzska commented Nov 20, 2021

about the restart policy - https://docs.docker.com/compose/compose-file/compose-file-v3/#restart_policy.

this error is about connection has been lost. How are you running the proxy?

I'm the following the Docker-compose (best way) method but I see that you've had a 60,000 timeout since I first setup the proxy. I'll try with this updated config and see if it makes a difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants