Repository navigation
[CRITICAL] [nextdns] Certificate hash not found #1808
Answered
by
jedisct1
MojtabaFaal
asked this question in
Q&A
|
Hi
I receive this CRITICAL error yesterday and today |
Answered by
jedisct1
Aug 8, 2021
Replies: 1 comment 1 reply
|
Looks like they just switched to a new certificate authority. Delete the |
1 reply
Answer selected by
MojtabaFaal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like they just switched to a new certificate authority.
Delete the
public-resolvers.mdfile and restart the server. It should load the new version.