does dehydrated support domain verification by https(port 443) #169

Closed
opened 2025-12-29 00:26:25 +01:00 by adam · 2 comments
Owner

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~
adam closed this issue 2025-12-29 00:26:26 +01:00
Author
Owner

@lukas2511 commented on GitHub (Dec 18, 2016):

Not yet, sorry.

@lukas2511 commented on GitHub (Dec 18, 2016): Not yet, sorry.
Author
Owner

@waja commented on GitHub (Jul 12, 2017):

This a duplicate of #271

@waja commented on GitHub (Jul 12, 2017): This a duplicate of #271
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#169