-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Odd error once in a while (wsarecvfrom) #320
Comments
I'm not quite sure what version of acme-dns I'm using.. there isn't a --version or something like that to check as far as I can tell. |
You would have to had to build acme-dns yourself or get someone to build it for you (last I checked it doesn't build without minor modification), there is no prebuilt version for Windows. That error is a standard windows sockets error and is not controlled by acme-dns, that said the exception should generally be caught and logged then processing should resume as public DNS is a very hostile place. If you have acme-dns running as a service you could just configure it to auto restart on failure. |
I must have done that then.. sorry it's been a while. I have it setup to auto restart on crash, just figured maybe we could somehow avoid the crash to begin with. Though if Windows isn't really supported to begin with: sorry for the trouble and feel free to close this out. |
Hey folks,
Once in a long while I get an error like this on Win10:
Then the process exits.
Any ideas about how we can not crash in this case? I have no idea what sends what message that leads to the crash.
The text was updated successfully, but these errors were encountered: