Sir_Kevin@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 1 day agoDebugginglemmy.dbzer0.comimagemessage-square40fedilinkarrow-up1844arrow-down17
arrow-up1837arrow-down1imageDebugginglemmy.dbzer0.comSir_Kevin@lemmy.dbzer0.com to Programmer Humor@programming.devEnglish · 1 day agomessage-square40fedilink
minus-squareRob Bos@lemmy.calinkfedilinkEnglisharrow-up4·20 hours agoNot all dns providers support acme, I’ve discovered to my recent annoyance. The one I use at work, for instance.
minus-squareElvith Ma'for@feddit.orglinkfedilinkarrow-up3·18 hours agoI already use certbot with my DNS provider, so it should generally be supported. And indeed, O found the docs, where all supported providers are listed. https://doc.traefik.io/traefik/https/acme/#providers
minus-squareRob Bos@lemmy.calinkfedilinkEnglisharrow-up2·14 hours agoYeah. For wildcard DNS from letsencrypt, you can’t do HTTP validation, only DNS, which involves creating a TXT record. Your DNS provider needs to run an ACME server, which runs an API that’ll add the required TXT records on request. As I understand it.
Not all dns providers support acme, I’ve discovered to my recent annoyance. The one I use at work, for instance.
I already use certbot with my DNS provider, so it should generally be supported. And indeed, O found the docs, where all supported providers are listed.
https://doc.traefik.io/traefik/https/acme/#providers
Yeah. For wildcard DNS from letsencrypt, you can’t do HTTP validation, only DNS, which involves creating a TXT record.
Your DNS provider needs to run an ACME server, which runs an API that’ll add the required TXT records on request.
As I understand it.