-
-
Notifications
You must be signed in to change notification settings - Fork 44
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 becames unresponsive after some time #34
Comments
Hm, i have the Container Running on Kubernetes and on "normal" Docker and do Not have any of these issues. Is the Docker deamon logs something? //EDIT: Could be related => mosajjal/sniproxy#76 |
in fact seems related to https://github.com/mosajjal/sniproxy/issues/76 however from my testing i pulled an older snidust image https://github.com/users/seji64/packages/container/snidust/103503017?tag=sha-40ae16a and that seems to work better as it only had a couple of hiccups in the last 12 hrs. Marking downstream cloudflare-dns (1.1.1.1:443) as 'up' not sure what has changed in newly images that is causing this issues. As a reference I'm on |
please note replacing sniproxy with nginx resulted in a breaking change. nginx is listening on port 8080 (before 80) and 8443 (before 443). Ensure you update your docker configuration accordingly! |
Hi - the container is working great and functional so far. it does a great job when can keep online, the problem I'm facing is that after a few minutes without processing queries or being idle like no one is using it the logs start showing entries like this:
2023-10-13T01:37:49Z ERR EOF service=http
and then, became totally unresponsive and need to restart the container to start working again. any idea why this may happen or do you know any workaround to keep it from losing the connection like this?
The text was updated successfully, but these errors were encountered: