grindsa

The change causes issues on my side as well. Seems `charset_normalizer` does not detect below ascii string correctly (even when using the newest 2.0.2 version) ```` >>> rawdata = b'g4UsPJdfzNkGW2jwmKDGDilKGKYtpF2X.mx3MaTWL1tL7CNn5U7DeCcodKX7S3lwwJPKNjBT8etY'...

I see this rather as CA function than a feature of the a2c proxy. But this does not mean that it cannot be done if the revocation method is supported...

hi, thank you for pointing this out. It makes perfect sense to increase this limit. Will work on it the upcoming days. BR Joern BTW. Are you using the django_handler?...

Fix finally made it into v.23. Closing the issue...

You could check the http[s]:///directory resource to verify that the container is up but this URL wont check the database-connection. If such check is needed let me know; we can...

Implementation is done (1082a240f2fb) and works fine. Some tests are still missing. I will leave this issue open till the changes will make it into master branch...

Change made it into v.23. Closing the issue...

Can you enable debugging in acme2certifer (option `debug: True` in `acme_srv.cfg`) and share the logs? The certbot version as well as the command line for enrollment you did use would...

Another thought coming into my mind: Certbot is not populating the CN field in the CSR. Could it be that your CA is mandating this and the above error message...

Thanks for troubleshooting yourself and for finding the root-cause. The remark to have an additional check for config-options starting or ending with " makes sense. I will implement this in...