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.

Sign up for GitHub

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

Jump to bottom

Listening port issue #334

Open

mvevitsis opened this issue Jan 27, 2025 · 1 comment

mvevitsis commented Jan 27, 2025

Since the latest mainline update, stopping/starting dnscrypt does not work correctly.

If you stop and restart it again with the same port, it will no longer properly capture DNS requests on that port.

The only way to "unstick" it is to change the listening port to something else (after this you can change it back if you want).

Owner

Gedsh commented Jan 30, 2025

This sounds very odd. Please provide a detailed description of what exactly you do step by step. And what kind of problem occurs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment