Replies: 1 comment 2 replies
-
|
Thanks for the detailed explanation, thatβs a really interesting use case, and definitely something Iβd like to support in Wiredoor in the future. At the moment, Wiredoor relies on HTTP validation for Let's Encrypt certificates, so for private/internal services without public DNS records, self-signed certs are the only option. But I agree, supporting DNS-01 challenges would be ideal in scenarios like yours. Iβm still exploring how to approach this technically. If you have any suggestions, tools, or workflows youβre currently using for DNS validation, Iβd really appreciate the input. It could help shape how we implement DNS-based certificate issuance in Wiredoor. Happy to collaborate or even accept a contribution if someone wants to help drive this feature forward. π |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently using Nginx Proxy Manager for my services. Some of them are internal only, some of them are exposed to the internet.
For the internal services I've set the subdomain (e.g.
internal-service-1.mydomain.com) in my local DNS to the IP of my Nginx Proxy Manager instance.There I forward it to the service and use a Let`s Encrypt certificate with DNS validation. Because of the DNS validation I do not need to set actual subdomain in the public DNS.
While I am planning to migrate my exposed services to wiredoor, I see the only chance to migrate the private services with a self signed certificate.
Would be nice if wiredoor could also use DNS challenges for this scenario
Beta Was this translation helpful? Give feedback.
All reactions