Stefan Eissing

np, @tatsuhiro-t, an opportunity to learn more about it.

That means during talking to the ACME server, it responded with HTTP code 413, indicating "Payload Too Large". Which is strange. What ACME servers do you use for the domain...

No work planned and not motivation to start that by myself in sight.

@bencew I believe tailscale changed their API for this. I did not have the time to follow this. I should update the documentation on this, I guess.

Updated the README.md to state that the described setup is now historical and no longer working.

The complication with how the TLS-ALPN-01 challenge works in Apache is that the "challenge" cert is *added* to the `SSL*` context of OpenSSL and does not replace the already existing...

I added the directives missing in the link list and a description of `MDCertificateCheck` in #368. Regarding other 2 directives mentioned in the Apache documentation: - `MDDriveMode` has been renamed...

Thanks for the report and the testing. Yes, the "busy looping" is exactly the problem without knowledge of an underlying file descriptor/socket to poll on.

This is a viable approach to address your use case. I would nudge it into a slightly more general direction: 1. Do you really need to error code and diagnostic...

@Mrida sorry, I am not really familiar with that part of the code. I recommend contacting the dev mailing list to get more attention at [email protected]