-
Notifications
You must be signed in to change notification settings - Fork 74
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
CLOSE_WAIT #148
Comments
@jedisct1 Would you have any ideas? |
Was there a known solution to this problem ? |
Yea I switched to this repo/branch jedisct1/dnscrypt-wrapper:xchacha-stamps since that is what the dnscrypt-server-docker image uses. This works very well in docker. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure but I think the wrapper is not closing closed connections properly:
good
As it happens
Bad (no more queries are being answered untill a dnscrypt-wrapper restart)
I'm using GCP with kubernetes. So traffic routed like this: GCP LoadBalancer->kubernetes-service->dnscrypt-wrapper-container->kubernetes-service->unbound-container
Restarting dnscrypt-wrapper temporarily fixes the problem
The text was updated successfully, but these errors were encountered: