vgist / dockerfiles

🐳 A collection of delicious docker recipes.
https://hub.docker.com/u/gists/
Apache License 2.0
164 stars 62 forks source link

Certificate Error for quad9 (9.9.9.9) #7

Closed adit-s closed 5 years ago

adit-s commented 5 years ago

Hello. I'm trying to use 9.9.9.9, but it keeps producing a certificate error.

Here is the command I use to run and then start the container: docker run \ -d \ --name dnscrypt-proxy \ -p 5353:5353/tcp \ -p 5353:5353/udp \ -e LOCAL_IP=0.0.0.0 \ -e LOCAL_PORT=5353 \ -e PROVIDER_NAME=2.dnscrypt-cert.quad9.net \ -e RESOLVER_IP=9.9.9.9 -e RESOLVER_PORT=8443 gists/dnscrypt-proxy

The docker logs show the following errors repeated: Mon Apr 15 00:45:36 2019 [NOTICE] Starting dnscrypt-proxy 1.9.5 Mon Apr 15 00:45:36 2019 [INFO] Generating a new session key pair Mon Apr 15 00:45:36 2019 [INFO] Done Mon Apr 15 00:45:36 2019 [ERROR] Suspicious certificate received Mon Apr 15 00:45:36 2019 [ERROR] No useable certificates found Mon Apr 15 00:45:37 2019 [INFO] Refetching server certificates Mon Apr 15 00:45:37 2019 [ERROR] Suspicious certificate received Mon Apr 15 00:45:37 2019 [ERROR] No useable certificates found Mon Apr 15 00:45:40 2019 [INFO] Refetching server certificates Mon Apr 15 00:45:40 2019 [ERROR] Suspicious certificate received Mon Apr 15 00:45:40 2019 [ERROR] No useable certificates found Mon Apr 15 00:45:46 2019 [INFO] Refetching server certificates Mon Apr 15 00:45:46 2019 [ERROR] Suspicious certificate received Mon Apr 15 00:45:46 2019 [ERROR] No useable certificates found

I tried adding the provider key, but it also gave an error. I got the following from the Quad9 site (I thought the minisign_key may work - "-e PROVIDER_KEY=RWQBphd2+f6eiAqBsvDZEBXBGHQBJfeG6G+wJPPKxCZMoEQYpmoysKUN"): [sources.quad9-resolvers] urls = ["https://www.quad9.net/quad9-resolvers.md"] minisign_key = "RWQBphd2+f6eiAqBsvDZEBXBGHQBJfeG6G+wJPPKxCZMoEQYpmoysKUN" cache_file = "quad9-resolvers.md" refresh_delay = 72 prefix = "quad9-"

Am I doing something wrong or using the wrong provider key. I'm not sure what the next step is to get it working and would appreciate any help.

Regards, AditS

adit-s commented 5 years ago

I needed to enter Quad9's public provider key which is 67c847b8c8758cd120245543be756746df34df1d84c00b8c470368df821d863e After that, it worked.

(from jedisct1 @ https://github.com/dyne/dnscrypt-proxy/issues/18)