Did you previously have an AAAA record for jkru.de? I don't see one now, but based on this output it appears that an IPv6 address was returned for a lookup for jkru.de at the time of the error.
Let's Encrypt recently began preferring IPv6 addresses when advertised which may be part of why this failed when it used to work.