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 becames unresponsive after some time #34

Closed
hogmac opened this issue Oct 13, 2023 · 3 comments · Fixed by #43
Closed

docker becames unresponsive after some time #34

hogmac opened this issue Oct 13, 2023 · 3 comments · Fixed by #43

Comments

@hogmac
Copy link

hogmac commented Oct 13, 2023

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?

@Seji64
Copy link
Owner

Seji64 commented Oct 13, 2023

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

@hogmac
Copy link
Author

hogmac commented Oct 13, 2023

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'
Marking downstream cloudflare-dns (1.0.0.1:443) as 'up'
Marking downstream dns.google (8.8.8.8:853) as 'up'
Marking downstream dns.google (8.8.4.4:853) as 'up'
PowerDNS DNSDist Security Update Mandatory: Upgrade now.
2023-10-13T07:10:59Z ERR http: no Host in request URL service=http
2023-10-13T07:15:07Z ERR http: no Host in request URL service=http

PowerDNS DNSDist Security Update Mandatory: Upgrade now.

not sure what has changed in newly images that is causing this issues. As a reference I'm on Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1. I will keep testing the image version I pulled to see if becomes more stable at some point.

@Pachini Pachini mentioned this issue Mar 31, 2024
@Seji64 Seji64 linked a pull request Apr 2, 2024 that will close this issue
@Seji64 Seji64 closed this as completed in #43 Apr 2, 2024
Seji64 added a commit that referenced this issue Apr 2, 2024
@Seji64
Copy link
Owner

Seji64 commented Apr 2, 2024

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!

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

Successfully merging a pull request may close this issue.

2 participants