You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log:
[2024-08-07 13:15:46] [NOTICE] dnscrypt-proxy 2.1.5
[2024-08-07 13:15:46] [NOTICE] Service is not usable yet
[2024-08-07 13:15:46] [NOTICE] Resolving server host [raw.githubusercontent.com] using bootstrap resolvers over udp
[2024-08-07 13:15:46] [NOTICE] Service is not usable yet
[2024-08-07 13:15:46] [NOTICE] Resolving server host [quad9.net] using bootstrap resolvers over udp
[2024-08-07 13:15:47] [CRITICAL] Unable to retrieve source [quad9-resolvers]: [Incompatible signature algorithm]
[2024-08-07 13:15:47] [FATAL] Incompatible signature algorithm
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Quad9 are publishing resolvers lists on their website and on GitHub: https://github.com/Quad9DNS/dnscrypt-settings
If you're using the DNSCrypt public list of resolvers, you don't need to use them, as the Quad9 resolvers are already included.
But if you are fetching the Quad9 lists from them directly, you may have seen issues related to signatures since yesterday.
They changed the signing key: Quad9DNS/dnscrypt-settings#7
So, the following changes are required to your
dnscrypt-proxy
configuration file:Replace:
minisign_key = "RWQBphd2+f6eiAqBsvDZEBXBGHQBJfeG6G+wJPPKxCZMoEQYpmoysKUN"
With:
minisign_key = "RWTp2E4t64BrL651lEiDLNon+DqzPG4jhZ97pfdNkcq1VDdocLKvl5FW"
Beta Was this translation helpful? Give feedback.
All reactions