bitbeans
DNSCrypt Service sometimes isn't starting
Greetings! Sometimes, like 1/10 startups, the DNSCrypt Service just won't start on its own. Don't know why, don't know how. All I know is that sometimes my connection just won't work until I manually start the service.
Write what you need and I'll supply you with whatever info you need.
I can't start it as well.
I keep trying hinting the starting button but nothing happened
start WindowsPower Shell as administrator:
cd "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy"
.\dnscrypt-proxy.exe
Are any errors displayed there? Which operating system is used?
Windows 10 Pro lastest release
It seems indicating that the argument is invalid
@Rictusempra First Command: cd "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy" Press ENTER Second Command: .\dnscrypt-proxy.exe Press ENTER
No error (all [NOTICE] messages) this time but I still failed to start the service
@Rictusempra
cd "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy"
.\dnscrypt-proxy -service install
.\dnscrypt-proxy -service start
3 Commands :)
@Rictusempra i can`t say. Maybe the service was not installed correctly. Is this the first version you have installed?
After auto update to 2.0.6, the service can't start.
.\dnscrypt-proxy -service install
.\dnscrypt-proxy -service start
Any comment ?
W10 Pro x64 with Bitdefender Antivirus.
Try going into regedit and manually delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\dnscrypt-proxy
My problem caused by the Antivirus. It detected below suspicious file and automatically put it into quarantine zone which make the installation corrupted. Gen:Variant.Graftor.471159
If I deactivated the AV and do installation, adding DNScrypt into whitelist, then the program work like a charm. Definitely can't install when AV is active.
@Dyras are you also using hibernation: https://github.com/bitbeans/SimpleDnsCrypt/issues/255 ?
I also confirm this problem. Tested on Windows 10 1709 x64 and Windwos 7 SP1 x64. Occurs at system startup or after waking up from sleep with an approximate frequency 1/10. Used AV: Comodo Internet Security 10.2.0.6514. System Log:
Error Service Control Manager 7009
A timeout was reached (30000 milliseconds) while waiting for the DNSCrypt client proxy service to connect.
Error Service Control Manager 7000
The DNSCrypt client proxy service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
I don't know much about Comodo Internet Security, or about AVs in general, but they include a copy of an older dnscrypt-proxy version in some of their products. Maybe both are fighting to acquire the same port number after a wakeup.
Hi, I'm also experiencing this problem. It's been about 2 weeks since I updated to the new interface, already encountered this problem about 3-4 times. I never encountered this problem with the old interface. Should I downgrade?
Windows 10 64 bit 1709
I have the same problem:
- Windows 10 Pro 64-bit 1709
- Latest .NET framework
- PPPoE internet connection (manually enabled after Windows Login)
- Starting dnscrypt-proxy.exe from the command-line is OK. After that the service can be started.
- Log file: 2018-03-21 17_17_24_Error.log
I also have this issue basically every startup, I have no AV, and it always starts up fine for me if I go in after boot and manually start dnscrypt. 2018-03-27 09_17_49_Error.log
https://github.com/jedisct1/dnscrypt-proxy/issues/234 Same issue here in event log and a solution
could it be that the fallback dns isn't working, so it can't update the public-resolvers.md on startup and then the service fails? would like together a few of the issues open in the project atm.
Why was this closed?
It's for sure an issue.
On 64bit Windows 10 1709:
C:\Program Files (x86)\bitbeans\Simple DNSCrypt\dnscrypt-proxy>dnscrypt-proxy -service start [2018-04-02 19:23:43] [NOTICE] Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded [2018-04-02 19:23:43] [NOTICE] dnscrypt-proxy 2.0.4 [2018-04-02 19:23:43] [NOTICE] Service started
Yet service is NOT running and Event Viewer > System shows:
The DNSCrypt client proxy service terminated unexpectedly.
After my first reboot after installation, my service did not start either. The event log reveals the following error:
A timeout was reached (30000 milliseconds) while waiting for the DNSCrypt client proxy service to connect.
The DNSCrypt client proxy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
I just want to report about what happened since my last post here. I downgraded to 0.4.3 and I never get this service not starting problem since then. So I'm sure something is wrong with the new version not my computer.
One thing I noticed when using new version, the server list was empty when the service failed to start. I think maybe the old version worked because it stored the server list somewhere before downloading new list?
Hi, I also experienced problems when my client upgraded to a newer version.
In my case the problems were caused by EMET (on Windows 10 and on Windows 7).
I had configured a rule for "dnscrypt-proxy" in EMET and the newer client doesn't like the EAF protection. You don't have to delete the complete rule in EMET, just disable EAF.
If you have the latest version of Windows 10,then EMET has been replaced with Exploit Guard, interestingly I had no issues with Exploit Guard, although it also uses EAF.
Finally, my antivirus-software (emsisoft) flagged (the behavior of) dnscrypt-proxy as malicious. Not sure what the new client does so differently, but it seems to trigger responses from anti-virus software and you have to keep an eye on your anti-virus software too.
Correction: I have an issue on Windows 10 now, but my best bet is that it is caused by my configuration in Exploit Guard... will create a rule for dnscrypt-proxy (without EAF at least) to see if that solves my problem.