Hello Miyo,
it might be a bit late for a reply. However, see my solution below.
On Tue, 23 Jun 2020, miyo wrote:
dnscrypt-proxy is configured [1] to listen 127.0.0.1:5300 due to dnsmasq
listening on port 53.
[1] in both /etc/dnscrypt-proxy/dnscrypt-proxy.toml and
/lib/systemd/system/dnscrypt-proxy.socket
Package upgrade overwrites changes in /lib/systemd/system/dnscrypt-proxy.socket
and dnscrypt-proxy fails to start.
That is correct! You better shouldn't change anything in /lib/systemd/
or /usr/lib/systemd/, but you could rather make a copy of
/lib/systemd/system/dnscrypt-proxy.socket in /etc/systemd/system/ and
make your changes there. Local changes to configuration files in /etc/
are not overwritten during an upgrade. Moreover, you don't need to set
the listening port in /etc/dnscrypt-proxy/dnscrypt-proxy.toml if
dnscrypt-proxy is a service managed by systemd. In this case,
dnscrypt-proxy always binds to the systemd sockets.
Before copying dnscrypt-proxy.socket to /etc/systemd/system/, you need to
temporarily disable the socket file by calling:
systemctl disable dnscrypt-proxy.socket
systemctl stop dnscrypt-proxy.socket
After having changed /etc/systemd/system/dnscrypt-proxy.socket, you only
have to tell systemd the following:
systemctl daemon-reload
systemctl enable dnscrypt-proxy.socket
systemctl restart dnscrypt-proxy.service
... and you are done.
Best regards,
Thomas Uhle
