WorkingDirectory setting of systemd unit file is bogus

[CongoKong]

What's happening?

the WorkingDirectory of the dnscrypt-proxy systemd unit file is the folder used during install of dnscrypt-proxy, i.e. a home directory of an user. dnscrypt-proxy still works (probably due to a fallback), but this is not correct. dnscrypt-proxy should use its own directory as WorkingDirectory.

Diagnostic output

Please run these commands and paste the output:

./dnscrypt-proxy -version
2.1.18

./dnscrypt-proxy -check
[2026-09-17 21:01:08] [NOTICE] Using default Weighted Power of Two (WP2) load balancing strategy
[2026-09-17 21:01:08] [NOTICE] Source [relays] loaded
[2026-09-17 21:01:08] [NOTICE] Source [public-resolvers] loaded
[2026-09-17 21:01:08] [NOTICE] Configuration successfully checked

./dnscrypt-proxy -resolve example.com
Resolving [example.com] using 127.0.0.1 port 5354

Resolver      : 185.213.155.123

Canonical name: example.com.

IPv4 addresses: 104.20.23.154, 172.66.147.243
IPv6 addresses: 2606:4700:10::ac42:93f3, 2606:4700:10::6814:179a

Name servers  : hera.ns.cloudflare.com., elliott.ns.cloudflare.com.
DNSSEC signed : yes
Mail servers  : 1 mail server found

HTTPS alias   : -
HTTPS info    : [alpn]=[h2], [ipv4hint]=[104.20.23.154,172.66.147.243], [ipv6hint]=[2606:4700:10::6814:179a,2606:4700:10::ac42:93f3]

Host info     : -
TXT records   : v=spf1 -all, _k2n1y4vw3qtb4skdx9e7dxt97qrmmq9

When does this occur?

during installation of dnscrypt-proxy.service

Where does it happen?

on linux variants using systemd (tested on debian, ubuntu)

How do we replicate the issue?

1. perform an installation of dnscrypt-proxy
2. check WorkingDirectory config of /etc/systemd/system/dnscrypt-proxy.service

Expected behavior

dnscrypt-proxy should use its own folder as working directory.

[jedisct1]

Paths are relative to the dnscrypt-proxy executable.

So it looks like it works as intended.

The generic installation instructions say to uncompress the archive, open the decompressed directory, modify config files there if needed, then type ./dnscrypt-proxy and if you want to install that as a permanent service, type ./dnscrypt-proxy -service install.

So everything is self-contained. In that context, paths must be relative to the executable file.