
                    For zerossl, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

@Dabada why did you close this issue? Even if it works in alastaircoote/docker-letsencrypt-nginx-proxy-companion it doesn't mean that it works in the JrCs version (=this repository)

acme companion DeserializationError: Deserialization error: Wrong directory fields

@JrCs that's a bit of a shame as such functionality would be useful in some dev workflows but I understand your view 

acme companion Self-signed for development

An experimental version of this feature inspired by @ymettier PR #220 has been added to dev This instructions are here Any feedback is welcome. 

acme companion Standalone Certificate

I was about to open the exact same issue! 😅
I had been using an older acme.sh version; today I decided to update it and start using Cloudflare's new tokens instead of the global API key