It seems that the pi-hole can’t forward requests to dnscrypt, as I can connect to the pi-hole with the clients of my network and I can see it processing the clients requests but the clients can’t reach the internet.
Also, when I ask dnscrypt-proxy to resolve some url from the terminal it gives me a timeout error. Seems also that no other processes are using the port 53.
Further, the raspberry running pi-hole is using opendns’s dns that where originally set up by pi-hole… any suggestion to solve this? I noticed that the opendns’s dns have been written into /etc/dhcpcd.conf, maybe I can just modify that file with the 127.0.0.1?
The instructions were very clear, I don’t understand what I am missing… Thank you!
That sounds like an issue with dnscrypt-proxy rather than Pi-hole.
Most likely, Pi-hole would run into the same timeouts when forwarding queries.
Inspecting Pi-hole's logs (e.g. by pihole -t) would confirm this if it's showing forwards to your proxy, with no answer ever received.
It's like you say, I can just see forwards with no replies. I believe the same, but I've installed dnscrypt-proxy lots of time in the past with no issues and I can't figure it out... Ip addresses seems ok.
EDIT: Not sure why, but I've changed the dnscrypt-proxy listening port from 5353 to 5300 (and same on the pi-hole) and started to work. I couldn't see anything else using the port 5353 nor the 53 before...
Glad it's working for you. Maybe you were just missing a restart.
Port 5353 is in use by the mDNS protocol, as implemented e.g. by Apple's bonjour or Linux' avahi, and Windows added native support in Win10 sometime in 2019.
Port 5300 is also reserved, for cluster heartbeats, but you won't run into any conflicts if you don't run such a cluster to make use of it in your local network.