Thanks for taking the time to report a bug! Before filing, please note:
Need help or have a question? The issue tracker is for confirmed, reproducible bugs only. For installation help, configuration help, troubleshooting, or general questions, please read the documentation first. If you still need assistance, use our Q&A Discussions instead - you'll likely get a faster response there.
Before submitting
Please make sure:
- You've read the documentation and this is not answered there already
- You're running the latest version of
dnscrypt-proxy (precompiled binaries from this repository)
- The software is correctly installed and configured
- You can reliably reproduce the issue
If the bug requires specific steps to reproduce, please include detailed instructions that would work on a fresh install of macOS, Windows, OpenBSD, or Ubuntu Linux.
Not sure if it's a bug? Start a discussion first - we're happy to help figure it out.
Diagnostic output
Please run these commands and paste the output:
What's happening?
https://dnscrypt.info/stamps/ has "Plain DNS" as an option, yet when I add generated stamp into dnscrypt-proxy, it returns
[ERROR] Unsupported protocol for [test]: [Plain]
When does this occur?
Where does it happen?
How do we replicate the issue?
- https://dnscrypt.info/stamps/
- Enter 192.168.34.56 (or any IP)
- Get DNSStamp and add it as static entry to dnscrypt-proxy's toml
- Start dnscrypt-proxy
Expected behavior
DNSCrypt-proxy test and connect to it, with or without encryption warning.
Additional context
Other DOH client have an option to use system's certstore to verify the cert, but DOH breaks frequently with dnscrypt-proxy. By adding 1 or 2 Plain DNS as a fallback (when no alternatives are online) this improves reliability.
Thanks for taking the time to report a bug! Before filing, please note:
Need help or have a question? The issue tracker is for confirmed, reproducible bugs only. For installation help, configuration help, troubleshooting, or general questions, please read the documentation first. If you still need assistance, use our Q&A Discussions instead - you'll likely get a faster response there.
Before submitting
Please make sure:
dnscrypt-proxy(precompiled binaries from this repository)If the bug requires specific steps to reproduce, please include detailed instructions that would work on a fresh install of macOS, Windows, OpenBSD, or Ubuntu Linux.
Not sure if it's a bug? Start a discussion first - we're happy to help figure it out.
Diagnostic output
Please run these commands and paste the output:
What's happening?
https://dnscrypt.info/stamps/ has "Plain DNS" as an option, yet when I add generated stamp into dnscrypt-proxy, it returns
[ERROR] Unsupported protocol for [test]: [Plain]When does this occur?
Where does it happen?
How do we replicate the issue?
Expected behavior
DNSCrypt-proxy test and connect to it, with or without encryption warning.
Additional context
Other DOH client have an option to use system's certstore to verify the cert, but DOH breaks frequently with dnscrypt-proxy. By adding 1 or 2 Plain DNS as a fallback (when no alternatives are online) this improves reliability.