I installed this. Configured it. Then I made a backup.
Then I removed it.
I rebooted router.
I installed it again and tried to restore the backup.
Error attached.
Dnscrypt-proxy -check fails when checking the .toml file and claims the bind address is in use. The issue doesnt start happening until you reconfigure. This was experienced by two and reported by 2 users and myself already.
Dnscrypt-proxy -check fails when checking the .toml file and claims the bind address is in use. The issue doesnt start happening until you reconfigure. This was experienced by two and reported by 2 users and myself already.
I think mine was working earlier on because I did manually done this step.
I didn’t know this is a problem and yes, when I first upgraded to this new version, dnscrypt-proxy didn’t start and the toml was renamed with the .err. Then I proceed to rename the example toml and configure the toml manually without the installer then I restart dnscrypt-proxy manually.
but meanwhile I still can use this latest version (2.0.43) as long as I don’t do re-configuration?
If we restart router, will it affect it from starting?
I think mine was working earlier on because I did manually done this step.
I didn’t know this is a problem and yes, when I first upgraded to this new version, dnscrypt-proxy didn’t start and the toml was renamed with the .err. Then I proceed to rename the example toml and configure the toml manually without the installer then I restart dnscrypt-proxy manually.
but meanwhile I still can use this latest version (2.0.43) as long as I don’t do re-configuration?
If we restart router, will it affect it from starting?
Info: Detected ARMv7 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.6
Info: DNSCRYPT_VER=2.0.43
Info: Manager file is Up-To-Date!
Info: Choose what you want to do:
1) Install/Update dnscrypt-proxy
2) Uninstall dnscrypt-proxy
3) Configure dnscrypt-proxy
4) Set timezone
5) Unset timezone
6) Install (P)RNG
7) Uninstall (P)RNG
8) Install swap file
9) Uninstall ALL
b) Backup
r) Restore
q) Quit
=> Please enter the number that designates your selection:, [1-9/b/r/q]: 3
Info: This operation allows you to configure dnscrypt-proxy
=> Do you want to proceed? [y/n]: y
Info: Configuring dnscrypt-proxy...
Info: Checking dnscrypt-proxy configuration...
[2020-06-10 21:42:33] [NOTICE] dnscrypt-proxy 2.0.43
[2020-06-10 21:42:33] [NOTICE] Network connectivity detected
[2020-06-10 21:42:33] [FATAL] listen udp 127.0.1.1:53: bind: address already in use
*** Error: Skipping this test until next version...
Info: Found previous dnscrypt-proxy config file
Info: How do you want to reconfigure:
Info: 1) Start from previous settings file
Info: 2) Start from default config
=> Your selection, [1-2]: 2
Info: Checking dnscrypt-proxy configuration...
[2020-06-10 21:44:35] [NOTICE] dnscrypt-proxy 2.0.43
[2020-06-10 21:44:35] [NOTICE] Network connectivity detected
[2020-06-10 21:44:35] [FATAL] listen udp 127.0.1.1:53: bind: address already in use
*** Error: Skipping this test until next version...
Info: Restarting dnscrypt-proxy with new config...
Info: Operation completed. You can quit or continue
Jun 10 21:44:35 izzt: Start dnscrypt-proxy
Jun 10 21:44:36 dnscrypt-proxy[1714]: dnscrypt-proxy 2.0.43
Jun 10 21:44:36 dnscrypt-proxy[1714]: Network connectivity detected
Jun 10 21:44:36 dnscrypt-proxy[1714]: Dropping privileges
Jun 10 21:44:36 dnscrypt-proxy[1714]: Network connectivity detected
Jun 10 21:44:36 dnscrypt-proxy[1714]: Now listening to 127.0.1.1:53 [UDP]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Now listening to 127.0.1.1:53 [TCP]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Source [public-resolvers] loaded
Jun 10 21:44:36 dnscrypt-proxy[1714]: Source [relays] loaded
Jun 10 21:44:36 dnscrypt-proxy[1714]: Anonymized DNS: routing everything via [anon-cs-se anon-sth-se]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Firefox workaround initialized
Jun 10 21:44:53 dnscrypt-proxy[1714]: Server with the lowest initial latency: soltysiak (rtt: 34ms)
Jun 10 21:44:53 dnscrypt-proxy[1714]: dnscrypt-proxy is ready - live servers: 23
Info: Detected ARMv7 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.6
Info: DNSCRYPT_VER=2.0.43
Info: Manager file is Up-To-Date!
Info: Choose what you want to do:
1) Install/Update dnscrypt-proxy
2) Uninstall dnscrypt-proxy
3) Configure dnscrypt-proxy
4) Set timezone
5) Unset timezone
6) Install (P)RNG
7) Uninstall (P)RNG
8) Install swap file
9) Uninstall ALL
b) Backup
r) Restore
q) Quit
=> Please enter the number that designates your selection:, [1-9/b/r/q]: 3
Info: This operation allows you to configure dnscrypt-proxy
=> Do you want to proceed? [y/n]: y
Info: Configuring dnscrypt-proxy...
Info: Checking dnscrypt-proxy configuration...
[2020-06-10 21:42:33] [NOTICE] dnscrypt-proxy 2.0.43
[2020-06-10 21:42:33] [NOTICE] Network connectivity detected
[2020-06-10 21:42:33] [FATAL] listen udp 127.0.1.1:53: bind: address already in use
*** Error: Skipping this test until next version...
Info: Found previous dnscrypt-proxy config file
Info: How do you want to reconfigure:
Info: 1) Start from previous settings file
Info: 2) Start from default config
=> Your selection, [1-2]: 2
Info: Checking dnscrypt-proxy configuration...
[2020-06-10 21:44:35] [NOTICE] dnscrypt-proxy 2.0.43
[2020-06-10 21:44:35] [NOTICE] Network connectivity detected
[2020-06-10 21:44:35] [FATAL] listen udp 127.0.1.1:53: bind: address already in use
*** Error: Skipping this test until next version...
Info: Restarting dnscrypt-proxy with new config...
Info: Operation completed. You can quit or continue
Jun 10 21:44:35 izzt: Start dnscrypt-proxy
Jun 10 21:44:36 dnscrypt-proxy[1714]: dnscrypt-proxy 2.0.43
Jun 10 21:44:36 dnscrypt-proxy[1714]: Network connectivity detected
Jun 10 21:44:36 dnscrypt-proxy[1714]: Dropping privileges
Jun 10 21:44:36 dnscrypt-proxy[1714]: Network connectivity detected
Jun 10 21:44:36 dnscrypt-proxy[1714]: Now listening to 127.0.1.1:53 [UDP]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Now listening to 127.0.1.1:53 [TCP]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Source [public-resolvers] loaded
Jun 10 21:44:36 dnscrypt-proxy[1714]: Source [relays] loaded
Jun 10 21:44:36 dnscrypt-proxy[1714]: Anonymized DNS: routing everything via [anon-cs-se anon-sth-se]
Jun 10 21:44:36 dnscrypt-proxy[1714]: Firefox workaround initialized
Jun 10 21:44:53 dnscrypt-proxy[1714]: Server with the lowest initial latency: soltysiak (rtt: 34ms)
Jun 10 21:44:53 dnscrypt-proxy[1714]: dnscrypt-proxy is ready - live servers: 23
As @Zastoff has alluded to, a temporary workaround has been added to allow versions of dnscrypt-proxy 2.0.43 to be used with the exception that the .toml files will not be able to be checked for containing content errors or improper formatting. Due to recent settings changes in Dnscrypt-proxy 2, a check for Netprobe was added to the dnscrypt-proxy 2 error checking functionality. This caused an improper FATAL flag to claim the udp listening address was already in use (when in fact it was being used by dnscrypt-proxy). In lieu of this, the installer will skip doing this check until the next DNSCRYPT-PROXY2 release for installations currently running version 2.0.43. The devs of Dnscrypt-proxy2 have already patched this, but it will not be included until the next release.
Yes you have to do a new .toml file because the new version remote dnscrypt proxy 2 version has added strings to the .toml file that are now mandatory to be there. Unless you go to the dnscrypt-proxy 2 site and manually add the strings yourself to the .toml file.
Now DnsCrypt worked for a few weeks and from today on problems.
--
Jun 13 15:01:02 lul dnscrypt-proxy[7829]: Unable to load the configuration file [/jffs/dnscrypt/dnscrypt-proxy.toml] -- Maybe use the -config command-line switch?
Jun 13 15:01:12 lul GLM2900: Warning: dnscrypt-proxy is dead
Jun 13 15:01:12 lul GLM2900: Start dnscrypt-proxy
Jun 13 15:01:12 lul dnscrypt-proxy[9202]: Unable to load the configuration file [/jffs/dnscrypt/dnscrypt-proxy.toml] -- Maybe use the -config command-line switch?
Info: Detected ARMv8 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.6
Info: DNSCRYPT_VER=2.0.44
Info: Manager file is Up-To-Date!
Info: Choose what you want to do:
--
Now DnsCrypt worked for a few weeks and from today on problems.
--
Jun 13 15:01:02 lul dnscrypt-proxy[7829]: Unable to load the configuration file [/jffs/dnscrypt/dnscrypt-proxy.toml] -- Maybe use the -config command-line switch?
Jun 13 15:01:12 lul GLM2900: Warning: dnscrypt-proxy is dead
Jun 13 15:01:12 lul GLM2900: Start dnscrypt-proxy
Jun 13 15:01:12 lul dnscrypt-proxy[9202]: Unable to load the configuration file [/jffs/dnscrypt/dnscrypt-proxy.toml] -- Maybe use the -config command-line switch?
Info: Detected ARMv8 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.6
Info: DNSCRYPT_VER=2.0.44
Info: Manager file is Up-To-Date!
Info: Choose what you want to do:
--
Yea I have been following their releases but these past few they have change things that appear not listed in their change log, so it is hard to figure out what is wrong until someone reports something.