OVHcloud DNS API works with acme.sh. Use --dns dns_ovh. You need application key, secret, and consumer key from their API panel. Took me one hour to set up, runs for two years now.
What do you use for TLS certificates?
For OVHcloud specifically I used lego before switching to acme.sh. Lego has better error messages when the API rate limits you. OVHcloud's API is moody.
pablowild
Member
Following this thread. My OVHcloud VPS in Gravelines needs love too.
pablowild said:
Following this thread
Please do not post "following" or "subscribed". Use the thread notification button. Keeping signal high.
~be kind or be gone~
priya said:
Does anyone have experience with OVHcloud DNS API specifically
I do not use OVHcloud DNS but their VPS in Singapore. For DNS I use Cloudflare, acme.sh supports it well. The latency from Singapore to Cloudflare is excellent.
Another option: dehydrated. Also shell, also lightweight. I used it before acme.sh existed. Still maintained. If you want minimal dependencies it is worth comparing.
Network boot believer here. I deploy acme.sh via PXE to all my nodes. Single binary fetch in the boot script, cron installed before the system is even "installed". Certificate automation from day zero.
boot anything, anywhere, anytime
What about Caddy? Handles TLS automatically, no separate tool needed.
nuyekigor
Member
matt30 said:
What about Caddy
Caddy is a web server, not a certificate tool. The thread asked for TLS certificate tools, not full server replacements. Different problem.
I use Traefik with Docker and it gets certificates from Let's Encrypt automatically. Not lightweight if you do not already run containers, but if you do, it is zero extra work.