Originally created by @barsara on GitHub (Dec 5, 2016).
Hi
As what we know, http and dns is used to verify domain owner in common.
But our customer site block http(port 80) and they don't have right or skill to modify dns record, the only chance for us to verify domain owner is https(port 443).
Does dehydrated support domain verification by https(port 443), like letsencrytp-auto
--standalone-supported-challenges http-01 to use port 80
--standalone-supported-challenges tls-sni-01 to use port 443
Thank in advance~
Originally created by @barsara on GitHub (Dec 5, 2016).
Hi
As what we know, http and dns is used to verify domain owner in common.
But our customer site block http(port 80) and they don't have right or skill to modify dns record, the only chance for us to verify domain owner is https(port 443).
Does dehydrated support domain verification by https(port 443), like letsencrytp-auto
--standalone-supported-challenges http-01 to use port 80
--standalone-supported-challenges tls-sni-01 to use port 443
Thank in advance~
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @barsara on GitHub (Dec 5, 2016).
Hi
As what we know, http and dns is used to verify domain owner in common.
But our customer site block http(port 80) and they don't have right or skill to modify dns record, the only chance for us to verify domain owner is https(port 443).
Does dehydrated support domain verification by https(port 443), like letsencrytp-auto
--standalone-supported-challenges http-01 to use port 80
--standalone-supported-challenges tls-sni-01 to use port 443
Thank in advance~
@lukas2511 commented on GitHub (Dec 18, 2016):
Not yet, sorry.
@waja commented on GitHub (Jul 12, 2017):
This a duplicate of #271