Arch Linux

matse

Member

Registered: 2011-04-27

Posts: 299

[SOLVED] dnscrypt-proxy - not working until service restart

Hi,

I have been using dnscrypt-proxy since some month now and since some days I have a strange problem:
If I boot and log in Gnome 3 with NetworkManager automatically connects to my wireless lan.
I can manually ping IP addresses (e.g. ping 8.8.8.8 works) but names get not resolved.

# systemctl status dnscrypt-proxy.service 
● dnscrypt-proxy.service - DNSCrypt-proxy client
   Loaded: loaded (/usr/lib/systemd/system/dnscrypt-proxy.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-05-24 07:34:09 CEST; 41s ago
     Docs: https://github.com/jedisct1/dnscrypt-proxy/wiki
  Process: 879 ExecStart=/usr/bin/dnscrypt-proxy --config /etc/dnscrypt-proxy/dnscrypt-proxy.toml (code=exited, status=255)
 Main PID: 879 (code=exited, status=255)

Mai 24 07:34:09 quark systemd[1]: Started DNSCrypt-proxy client.
Mai 24 07:34:09 quark dnscrypt-proxy[879]: Source [/var/cache/dnscrypt-proxy/public-resolvers.md] loaded
Mai 24 07:34:09 quark dnscrypt-proxy[879]: dnscrypt-proxy 2.0.14
Mai 24 07:34:09 quark dnscrypt-proxy[879]: listen udp 127.0.0.1:53: bind: address already in use
Mai 24 07:34:09 quark systemd[1]: dnscrypt-proxy.service: Main process exited, code=exited, status=255/n/a
Mai 24 07:34:09 quark systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'.
Mai 24 07:34:09 quark systemd[1]: dnscrypt-proxy.service: Start request repeated too quickly.
Mai 24 07:34:09 quark systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'.
Mai 24 07:34:09 quark systemd[1]: Failed to start DNSCrypt-proxy client.

It says 127.0.0.1:53 already in use, but at this moment the output of:

# ss -lp 'sport = :domain'
Netid                  State                    Recv-Q                   Send-Q                                      Local Address:Port                                        Peer Address:Port 

shows that nothing is using it.

And

# systemctl status dnscrypt-proxy.socket
● dnscrypt-proxy.socket - DNSCrypt-proxy socket
   Loaded: loaded (/usr/lib/systemd/system/dnscrypt-proxy.socket; enabled; vendor preset: disabled)
   Active: failed (Result: service-start-limit-hit) since Thu 2018-05-24 07:34:09 CEST; 44s ago
     Docs: https://github.com/jedisct1/dnscrypt-proxy/wiki
   Listen: 127.0.0.1:53 (Stream)
           127.0.0.1:53 (Datagram)

After a

# systemctl restart dnscrypt-proxy.service

everything works fine, dnscrypt starts as it should and "ss" shows dnscrypt proxy
I didn't change any config and use dnscrypt also for caching and have disabled NetworkManagers dns resolution and adapted my resolv.conf.

Any suggestions?

Last edited by matse (2018-05-24 12:55:27)

malteo

Member

Registered: 2008-04-05

Posts: 3

Re: [SOLVED] dnscrypt-proxy - not working until service restart

I have got the exact same problem since a couple of days

Everette88

Member

Registered: 2018-02-17

Posts: 41

Re: [SOLVED] dnscrypt-proxy - not working until service restart

Disable dncrypt-proxy.socket: https://github.com/jedisct1/dnscrypt-pr … -391065039

matse

Member

Registered: 2011-04-27

Posts: 299

Re: [SOLVED] dnscrypt-proxy - not working until service restart

Thanks, that solved the problem for me.
Would have really be nice, if the packager had given us a warning during the update process - nervertheless it works now with disabled socket, thanks for the help!