Bug#963532: dnscrypt-proxy: fails to start after upgrade when using custom port

2022-12-10 Thread Thomas Uhle
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/dnscr

Bug#963532: dnscrypt-proxy: fails to start after upgrade when using custom port

2020-06-23 Thread miyo
Package: dnscrypt-proxy Version: 2.0.39+ds1-2 Severity: important 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