Unable to run as a service if I use custom Bind Port.

[meluvalli]

As per description, if you try to run as a service, it fails if you specify a custom port to bind to. However, if you launch it manually with

sudo dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml

It runs fine. So, just can't run it as a service!

I have tried deleting the service and readding it using the below commands with no luck:

sudo systemctl stop dnscrypt-proxy.service
sudo systemctl stop dnscrypt-proxy.socket
sudo systemctl disable dnscrypt-proxy.socket
sudo systemctl disable dnscrypt-proxy.service
sudo rm /lib/systemd/system/dnscrypt-proxy.service /lib/systemd/system/dnscrypt-proxy.socket
sudo rm /var/lib/systemd/deb-systemd-helper-enabled/dnscrypt-proxy.service.dsh-also /var/lib/systemd/deb-systemd-helper-enabled/dnscrypt-proxy.socket.dsh-also /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/dnscrypt-proxy.service /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/dnscrypt-proxy.socket
sudo systemctl daemon-reload
sudo systemctl reset-failed
sudo dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml -service install
sudo service dnscrypt-proxy start

Config:

# Empty listen_addresses to use systemd socket activation
listen_addresses = ['127.0.0.1:54']
server_names = ['adguard-dns-doh']

[meluvalli]

Come to find out, when I looked at the "/etc/systemd/system/dnscrypt-proxy.service" file, it didn't have the -config parameter included!

I edited the file and changed the ExecStart Line to:

ExecStart=/usr/sbin/dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml

Then ran

systemctl daemon-reload

And started the service!

sudo systemctl start dnscrypt-proxy

Now it works!

[Sr-psycho]

Greetings! same problem but on windows11. I change the port value and DNScrypt does not start. I want to use DNScrypt with adguard home. The files listed above are not available for Linux in Windows, of course.