I would also argue it's not a "simple copy" of KEY=VALUE from the Acme docs, as the Acme docs for Namecheap include double-quotes. So a "simple copy" would be something like export NAMECHEAP_USERNAME="<my-username>" where what is needed or Proxmox to work with the Namecheap API is...
Performing the following from the console of the server using curl:
https://api.namecheap.com/xml.response?ApiUser=<my-namecheap-username>&ApiKey=<my-namecheap-api-key>&UserName=<my-namecheap-username>&Command=namecheap.domains.dns.getHosts&ClientIp=<my-whitelisted-ip>&SLD=<my-sld>&TLD=<my-tld>...
Yes. I obtained an API key and followed the dns-01 instructions found here (https://pve.proxmox.com/wiki/Certificate_Management#sysadmin_certs_acme_dns_challenge) along with the guidance found in acme’s docs (https://github.com/acmesh-official/acme.sh/wiki/dnsapi#53-use-namecheap), which also...
Even following the docs, I cannot get PVE to write the TXT record to Namecheap. So I need to somehow obtain what that TXT record entry should be so I can manually add it to my Namecheap DNS so I can then make a call to renew and obtain the certificate through the GUI.
Is there a way through SSH to obtain the TXT record from LetsEncrypt such that I could initially configure LE SSL certs within a node and then simply make a renewal request through the GUI? Thus, the auto renewal of SSL certs would work going forward?
I ask as I've yet to find a workaround...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.