From Auckland: latency to Let's Encrypt is fine but latency to OVHcloud API in Sydney is painful. I moved my DNS to a local provider. acme.sh with --dns dns_nsd worked better for me.
What do you use for TLS certificates?
My electricity bill is already criminal. I run acme.sh on a Raspberry Pi 4 in Tokyo for home services. Uses maybe 0.1% CPU during renewal. Certbot would make the poor thing sweat.
8-char NTLM found in 4min 32sec
Has anyone tried step-ca for internal certificates? Not for Let's Encrypt but for a private CA. Different use case I know, but related to the automation discussion.
Kindly I have implemented acme.sh with OVHcloud DNS on three instances. The --dns dns_ovh option functions correctly after obtaining the correct credentials. Thank you all for guidance. For others: the consumer key generation requires the /auth/credential endpoint, this detail was missing in some guides.
minhdock
Member
I learning server very much. This thread help me understand why manual is bad. I will use acme.sh for my VPS in Da Nang. Thank you everyone.