Algo server is started but can't connect via wireguard

[CA2MI]

I have about 10 Algo servers that I'm running. I have one that has just stopped working. The server appears to be running fine, I can't see any errors in the start up. Wireguard appears to connect to it, but no traffic will pass through and it's like when wireguard connects it hits a dead end and not internet traffic will pass though. I've never had this issue and I'm not sure where to start looking for a cause or even logs to see what might be going on.

[CA2MI]

It appears that DNS is not working properly.

On my computer connected to the Algo server via wireguard, I can ping google at 216.58.204.14. But I can't ping google at "ping google"

On the Algo server i can ping google at "ping google.com" and I get a response without any issues.

[CA2MI]

maybe i need settings other places changed

root@localhost:/etc/dnscrypt-proxy# systemctl status dnscrypt-proxy --full
● dnscrypt-proxy.service - DNSCrypt-proxy client
Loaded: loaded (/lib/systemd/system/dnscrypt-proxy.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/dnscrypt-proxy.service.d
└─99-algo.conf
Active: failed (Result: exit-code) since Sun 2021-03-14 14:27:36 UTC; 26s ago
TriggeredBy: ● dnscrypt-proxy.socket
Docs: https://github.com/jedisct1/dnscrypt-proxy/wiki
Process: 2362 ExecStart=/usr/bin/dnscrypt-proxy --config /etc/dnscrypt-proxy/dnscrypt-proxy.toml (code=exited, status=255/EXCEPTION)
Main PID: 2362 (code=exited, status=255/EXCEPTION)

Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Now listening to 172.24.198.122:53 [TCP]
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Now listening to [fd00::8:c67a]:53 [UDP]
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Now listening to [fd00::8:c67a]:53 [TCP]
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Systemd sockets are untested and unsupported - use at your own risk
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Wiring systemd TCP socket #0, dnscrypt-proxy.socket, 127.0.2.1:53
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Wiring systemd UDP socket #1, dnscrypt-proxy.socket, 127.0.2.1:53
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: Source [public-resolvers] loaded
Mar 14 14:27:36 localhost dnscrypt-proxy[2362]: No servers configured
Mar 14 14:27:36 localhost systemd[1]: dnscrypt-proxy.service: Main process exited, code=exited, status=255/EXCEPTION
Mar 14 14:27:36 localhost systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'.
root@localhost:/etc/dnscrypt-proxy#

[CA2MI]

this is the setting -

server_names = ['cloudflare-doh-ip4-filter-pri', 'cloudflare-doh-ip4-filter-alt', 'cloudflare-doh-ip6-filter-pri', 'cloudflare-doh-ip6-filter-alt']

[davidemyers]

Try:

server_names = ['cloudflare']

[CA2MI]

David, Thanks for that. You fixed it. Thank you for taking the time on your sunday.

[davidemyers]

It's too bad Quad9 stopped working for you. You might want to report the issue here. Let them know where your server is located.

Quad9 is currently working for me from Amazon Lightsail us-east-1a with:

server_names = ['quad9-doh-ip4-filter-pri', 'quad9-doh-ip6-filter-pri']