Joona Hoikkala

You can do reverse proxying for `/register` and `/update` as you assumed, that will work. Your problem does come along with the DNS though. The acme-dns DNS server needs to...

...or, depending on acme-dns client in use, you can also use a non-standard HTTP(S) port, there's no requirement for hosting the API on port 443 (or 80 in that regard).

Oh absolutely. The organization is actually already in place, and I have been planning this move for quite a while now. The plan was probably too ambitious though, as I’m...

So to reiterate; I'm all up for this, the organization is in place and the [acme-dns](https://github.com/acme-dns/acme-dns) repository with the current master branch is mirrored there. I would like to have...

> Hey! In general I would like to support this great project and support you maintaining the source code and the issues. Would you like to discuss it face to...

The code looks good generally. Only one thing pops up: While I agree that having a proper UUID as username, the password itself doesn't provide much added security, it still...

Hi! Unfortunately there isn't a way to handle this currently. Adding a label to track this later on.

Thanks for this report, it's highly appreciated. I had to make some changes to how certmagic is used because they updated their whole API between the versions, but I believe...

The later actually seems to indicate that the listener is up. "method not allowed" is because acme-dns only does POST requests and the default for curl is GET. "method not...

Hi, It is. I have just been really busy lately! Thanks for the PR, I'll look into it within a few days.