You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once in a long while I get an error like this on Win10:
time="2022-11-01T22:46:15-07:00" level=fatal msg="read udp [::]:53: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself."
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:
csm10495
changed the title
Odd error once in a while
Odd error once in a while (wsarecvfrom)
Nov 2, 2022
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.
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: