Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68719 - [dnscrypt-proxy] Unable to load the configuration file
Attached to Project:
Community Packages
Opened by a (a) - Monday, 23 November 2020, 14:52 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 23 November 2020, 15:07 GMT
Opened by a (a) - Monday, 23 November 2020, 14:52 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 23 November 2020, 15:07 GMT
|
DetailsDescription:
With a new update from some months ago, `pacman` installs `dnscrypt-proxy.toml` in `/etc/dnscrypt-proxy/` but that new update search for that file only in the same folder as the program, so ```bash $ which dnscrypt-proxy /usr/bin/dnscrypt-proxy ``` So per default it just doesn't work like it used to Is there any solution for this (other than a workaround) Additional info: * package version(s) : latest * config and/or log files etc. * link to upstream bug report, if any : https://github.com/DNSCrypt/dnscrypt-proxy/issues/1517 Steps to reproduce: ```bash $ dnscrypt-proxy -check /etc/dnscrypt-proxy/dnscrypt-proxy.toml [2020-11-23 15:51:09] [FATAL] Unable to load the configuration file [dnscrypt-proxy.toml] -- Maybe use the -config command-line switch? $ dnscrypt-proxy -check -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml $ ``` |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 23 November 2020, 15:07 GMT
Reason for closing: Not a bug
Additional comments about closing: It's meant to be run from the systemd service/socket.
Monday, 23 November 2020, 15:07 GMT
Reason for closing: Not a bug
Additional comments about closing: It's meant to be run from the systemd service/socket.