w2c/letsencrypt-esxi

DNS challenge?

NoLooseEnds opened this issue · 6 comments

Do you think it would be possible to use the DNS challenge instead of HTTP? Then not public facing servers would also work.

I found this project that could be of help: https://github.com/Trim/acme-dns-tiny/

I don't think so, unfortunately. The project you linked relies on the dnspython toolkit (see here), which is not available on any python interpreter shipped with ESXi.

The only way I can imagine to get such a lib working on ESXi would be to manually transfer it via scp from another host after running the install script. In any case, nothing that could integrated into this script.

What do you think about acme.sh? https://github.com/acmesh-official/acme.sh

Doesn't work currently, as it depends on Unix tools like tr, which isn't shipped with ESXi.

Could I use other port instead of default 443 as my ISP blocked it, like "abc.esxi.com:4443" ?

Churro commented

Could I use other port instead of default 443 as my ISP blocked it, like "abc.esxi.com:4443" ?

Yes, I think so. Just give it a try.

I tried to use port 2222 and use the syntax like,
esxcfg-advcfg -s aaa.bbb.com:2222 /Misc/hostname
to change the new hostname. But the result seems not working. It shows the port 80 that be still requesting.