search

bitbeans / SimpleDnsCrypt

A simple management tool for dnscrypt-proxy
https://simplednscrypt.org
MIT License
2.31k stars 235 forks source link

DNSCrypt Service sometimes isn't starting #251

Open Dyras opened 6 years ago

Dyras commented 6 years ago

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.

rddim commented 6 years ago

Confirm. In my case 2/4 at this time. There is no error logs.

Yevgen16 commented 6 years ago

I confirm. There is such a problem. The service does not always start.

Riajyuu commented 6 years ago

I can't start it as well.

image

I keep trying hinting the starting button but nothing happened

bitbeans commented 6 years ago

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?

Riajyuu commented 6 years ago

Windows 10 Pro lastest release image

It seems indicating that the argument is invalid

bitbeans commented 6 years ago

@Rictusempra First Command: cd "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy" Press ENTER Second Command: .\dnscrypt-proxy.exe Press ENTER

Riajyuu commented 6 years ago

No error (all [NOTICE] messages) this time but I still failed to start the service

bitbeans commented 6 years ago

@Rictusempra 

cd "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy"
.\dnscrypt-proxy -service install
.\dnscrypt-proxy -service start

3 Commands :)

Riajyuu commented 6 years ago

image

working this time, thx.

But why not working on Simple DNSCrypt itself?

bitbeans commented 6 years ago

@Rictusempra i can`t say. Maybe the service was not installed correctly. Is this the first version you have installed?

Riajyuu commented 6 years ago

Is this the first version you have installed?

Sure

lltechguyll commented 6 years ago

After auto update to 2.0.6, the service can't start.

image

.\dnscrypt-proxy -service install image

.\dnscrypt-proxy -service start image

Any comment ?

W10 Pro x64 with Bitdefender Antivirus.

evilvibes commented 6 years ago

Try going into regedit and manually delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\dnscrypt-proxy

bitbeans commented 6 years ago

@lltechguyll

The system cannot find the file ....

is there a filename?

lltechguyll commented 6 years ago

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.

bitbeans commented 6 years ago

@lltechguyll https://github.com/jedisct1/dnscrypt-proxy/issues/205

Dyras commented 6 years ago

@bitbeans I don't have an AV and this still happens for me.

bitbeans commented 6 years ago

@Dyras are you also using hibernation: https://github.com/bitbeans/SimpleDnsCrypt/issues/255 ?

Dyras commented 6 years ago

@bitbeans Never hibernated in my entire life.

d3bil0x commented 6 years ago

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.
jedisct1 commented 6 years ago

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.

cobafesbuk commented 6 years ago

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

RmzH commented 6 years ago

I have the same problem:

nalyDylan commented 6 years ago

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.

war59312 commented 6 years ago

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.

Zero3 commented 6 years ago

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.

cobafesbuk commented 6 years ago

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?

Sonnenaufgang commented 6 years ago

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.

Sonnenaufgang commented 6 years ago

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.

rddim commented 6 years ago

Two days with disabled service 2018-04-13 20_11_53_Error.log 2018-04-16 22_40_39_Error.log

440cid commented 6 years ago

I confirm. DNSCrypt service never run automatically upon start up and my internet is disabled until I manually open Simple DNSCrypt GUI and enable the service.

I tried disabling EAF in Windows 10's Exploit Protection and it seems to do the trick for few start ups but today the DNSCrypt service fails to run on start up again.

p0k33m0n commented 6 years ago

[FIX?]

Adding reference to "DNScript service" fix problem on my system. Hope, it is not only coincidence.

You can simply do it in CMD: sc config dnscrypt-proxy depend= Winmgmt

440cid commented 6 years ago

@p0k33m0n Doesn't work for me. Service still failed to start sometimes after reboot.

This is not a fix but I find it convenient to make Windows run Simple DNSCrypt GUI every time the service fails to start on boot so you can manually enable it. Go to services->DNSCrypt client proxy-> Properties -> Recovery -> Select First failure: Run a Program, then Run Program, point it to SimpleDnsCrypt.exe

cs96and commented 6 years ago

Is there any update on this? Its quite annoying having to manually start the service everytime I reboot.

p0k33m0n commented 6 years ago

On my system, after adding dependencies as above, everything works fine since month.

BTW: You can check new version service: https://github.com/jedisct1/dnscrypt-proxy

BTW2: SimpleDnsCrypt project looks bad - almost 2 months without any update, with such critical bugs like non starting service, errors in saving configuration? Abandonware?

gashtal commented 6 years ago

I am also facing the same problem. Every once in a while, the service does not start automatically after reboot and I have to start it manually. I would expect this could be because the service tries to start before the network connection is up and hence, fails. I came across this commit for dnscrypt-proxy:

https://github.com/jedisct1/dnscrypt-proxy/commit/ce62981c44913f59a0d638397edf17ebd7da27bb

I am going to test the new version and see if it solves the problem.

Dyras commented 6 years ago

@p0k33m0n The last commit for Simple DNS Crypt was 2 days ago The last commit for DNSCrypt-Proxy was 4 days ago

I don't think either of them are abandoned. I agree that this should be a higher priority, but we have to remember that the developers (most likely) have lives outside of developing two free programs.

gashtal commented 6 years ago

Since updating to a newer version of dnscrypt-proxy manually with the fix I mentioned above, I have only encountered once in over 10 reboots that the DNSCrypt service failed to auto-start. I recommend people suffering from this issue to update dnscrypt-proxy manually.

B00ze64 commented 6 years ago

You can use SERVICES.MSC to edit the proxy service and ask Windows to restart it (up to 3 times) should it fail to start the first time. What I did is I added this line to the proxy-install script: sc failure dnscrypt-proxy reset= 3600 actions= restart/60000/restart/60000// which configures it to restart up to 2 times...

simoncpu commented 6 years ago

I've encountered this issue too where DNSCrypt doesn't start on boot. I also experienced the same issue with WSL and the suggested solution was to turn off fast boot; this temporary fix works for DNSCrypt as well. However, I still experience the same issue whenever I wake up my laptop that has automatically gone into sleep mode. It's kindda frustrating because Windows Hello doesn't work without Internet.

bitbeans commented 6 years ago

is there a problem with the pre-release version? eg: https://simplednscrypt.blob.core.windows.net/deploy/SimpleDnsCrypt/bin/x64/SimpleDNSCrypt_x64.zip (dnscrypt-proxy 2.0.14)

Sonnenaufgang commented 6 years ago

@bitbeans I have a problem with the pre-release version on Windows 10. The blacklist.txt seems to be not effective anymore. In other words the blacklist feature doesn't work anymore, but is was working before. Otherwise the new version is working: Service starts even when I have done a complete shutdown. Domains appear in my OpenDNS stats.

simoncpu commented 6 years ago

I can confirm that my issue has been resolved with the latest update. The service now starts properly even if I turn fast boot on. I'm currently using Simple DNSCrypt 0.5.5 (x64) [dnscrypt-proxy 2.0.14]. Thanks!

RicottaRichie commented 6 years ago

I'm having difficulties using Simple DNS Crypt Proxy for Windows 10. I keep clicking on the service and it won't work. I went on Windows Powershell and typed "C:\Program Files\bitbeans\Simple DNSCrypt x64\dnscrypt-proxy" .\dnscrypt-proxy.exe and that didn't help.

d3bil0x commented 6 years ago

After update to DNSCrypt 0.5.5 (x64) the problem still occurs. The Fast Boot is off. I noticed that the dnscrypt-proxy service does not start in the scenario when the system boots without any active network connection and even a manual attempt to start the service ends in failure:

PS C:\Windows\system32> ipconfig

Windows IP Configuration

Wireless LAN adapter Wi-Fi:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : home

Wireless LAN adapter Local Area Connection* 1:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

PS C:\Windows\system32> net start dnscrypt-proxy
The service is not responding to the control function.

but after establishing a connection (in this case Wi-Fi), the service can be started:

PS C:\Windows\system32> ipconfig

Windows IP Configuration

Wireless LAN adapter Local Area Connection* 1:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : home
   IPv4 Address. . . . . . . . . . . : 192.168.0.103
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

PS C:\Windows\system32> net start dnscrypt-proxy
The DNSCrypt client proxy service is starting.
The DNSCrypt client proxy service was started successfully.

Tested on Windows 10 Pro x64 1803

simoncpu commented 6 years ago

The problem still occurs from time to time. I can't narrow down the exact cause though.

On Tue, Jun 5, 2018 at 1:15 AM d3bil0x notifications@github.com wrote:

After update to DNSCrypt 0.5.5 (x64) the problem still occurs. The Fast Boot is off. I noticed that the dnscrypt-proxy service does not start in the scenario when the system boots without any active network connection and even a manual attempt to start the service ends in failure:

PS C:\Windows\system32> ipconfig

Windows IP Configuration

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : home

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

PS C:\Windows\system32> net start dnscrypt-proxy The service is not responding to the control function.

but after establishing a connection (in this case Wi-Fi), the service can be started:

PS C:\Windows\system32> ipconfig

Windows IP Configuration

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home IPv4 Address. . . . . . . . . . . : 192.168.0.103 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1

PS C:\Windows\system32> net start dnscrypt-proxy The DNSCrypt client proxy service is starting. The DNSCrypt client proxy service was started successfully.

Tested on Windows 10 Pro x64 1803

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitbeans/SimpleDnsCrypt/issues/251#issuecomment-394430709, or mute the thread https://github.com/notifications/unsubscribe-auth/AAH2UWJJs-aOHlhrK6QFlywKSDhVjkz6ks5t5Ws5gaJpZM4SZJCe .

zero77 commented 6 years ago

@bitbeans Would it be worth creating a scheduled task, as this will automatically start the service at start up or at login, all without having to do much extra work or debugging.

Also, it has built in options for what to do if the service fails to start.

d3bil0x commented 6 years ago

@zero77 Yes, the working temporary solution - the task triggered by the event as follow in the Task Scheduler:

1 2 3 4 5 6

zero77 commented 6 years ago

@d3bil0x Yes exactly although, I meant for it to be created automatically when Simple DNS Crypt is installed and not for users to create a task themselves.

gsarcov commented 6 years ago

has anyone tried 0.5.6 x64 on Windows 10 1803? This release resolved the issue for me. It might not have fixed it for others though. https://github.com/bitbeans/SimpleDnsCrypt/releases/tag/0.5.6