Closed
Description
I've been using this for my home automation and using home
as a tld with bind server locally. This was working great until the last week or so, now I can no longer create certs for domains like foo.home
.
After digging in the code (there is only a generic internal error
popup in the UI) it seems that the domain needs to respond with some sort of endpoint to prove it exists. Any reason for this change?
This makes it really difficult to have certificates locally as now I would need to set up a fake service somewhere publicly to serve this endpoint just so that the certificate "validation" will pass.
Metadata
Metadata
Assignees
Labels
No labels