![]() and it shows it's binding to that port: ss -lp 'sport = :domain' Udp UNCONN 0 0 127.0.0.53%lo:domain 0.0.0.0:*īut it'll start up manually just fine via: Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process when starting up during boot or restarting the service after boot, it fails after it cannot bind to 127.0.0.2:53 despite nothing else using that port when dnscrypt is shut down: ss -lp 'sport = :domain' I then edited the example file, then saved it as the configuration file. bin file, the dnscrypt-proxy.toml configuration file and the dnscrypt-proxy-example.toml example file. I upgraded to 2.1.2 by downloading the latest from the developer's website, shutting down dnscrypt, extracting the. I noticed that I was using dnscrypt-proxy 2.0.31, which I'd downloaded and installed via sudo apt install dnscrypt-proxy. Sudo dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml Main PID: 101109 (code=exited, status=255/EXCEPTION)ĭec 14 00:23:13 HP-Laptop systemd: Started DNSCrypt client proxy.ĭec 14 00:23:14 HP-Laptop dnscrypt-proxy: dnscrypt-proxy 2.0.31ĭec 14 00:23:14 HP-Laptop dnscrypt-proxy: Network connectivity detectedĭec 14 00:23:14 HP-Laptop dnscrypt-proxy: Source loadedĭec 14 00:23:14 HP-Laptop dnscrypt-proxy: Firefox workaround initializedĭec 14 00:23:14 HP-Laptop dnscrypt-proxy: listen udp 127.0.0.2:53: bind: permission deniedĭec 14 00:23:14 HP-Laptop systemd: rvice: Main process exited, code=exited, status=255/EXCEPTIONĭec 14 00:23:14 HP-Laptop systemd: rvice: Failed with result 'exit-code'. Process: 101109 ExecStart=/usr/sbin/dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml (code=exited, status=255/EXCEPTION) Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: enabled)Īctive: failed (Result: exit-code) since Wed 00:23:14 CST 6s ago When attempting to manually restart the service, it tries to start, then fails after it can't bind to 127.0.0.2:53.
0 Comments
Leave a Reply. |