add desec

[szaimen]

• This PR is best reviewable commit by commit
• The PR was tested and verified that it works locally
• The PR was completely or partially created with AI

Summary

• Integrates Desec into the AIO interface which simplifies the domain registration and domain setup.
• You can either create a new account directly or use an existing account.
• You have a button that you can open where the process will be done. After the process is done, the whole page reloads and you can continue with the setup.
• Caddy and dnsmasq community containers will be activated during the process which will take over the cert generation and enable split-brain dns.
• Community containers will work automatically for example Vaultwarden as the subdomains of the desec domain point automatically via a wildcard dns entry towards the main desec domain.
• Playwright tests are added to ensure that the system works as expected in the future
• the desec api is mocked via a small node js based file.
• the qa and other docs were updated to mention desec

[pabzm]

Step 1

Initially the form looks like this, which needs UX love:

• the left input is unstyled,
• the middle input placeholder isn't fully readable, therefore it's purpose is unclear,
• the purpose of the right input is unclear

Step 2

After submitting the form the page reloads, thus jumps to the top, and only some details in the wall of text changed, which are hard to find. Especially that the desec.io password needs to be saved is easy to miss. Also I find it complicated to figure out what to do next (there's the note in the text that I should "click the button below" after verifying my email address, but actually I first have to copy the password and re-enter my chosen hostname "slug"; also I find it just too much text to be helpful).

Step 3

After submitting I see this error:

Warning: file_get_contents(/var/www/docker-aio/community-containers/dnsmasq/dnsmasq.json): Failed to open stream: No such file or directory in /var/www/docker-aio/php/src/ContainerDefinitionFetcher.php on line 59

Slim Application Error

A website error has occurred. Sorry for the temporary inconvenience.

Backtrace from container log:

NOTICE: PHP message: Slim Application Error
Type: JsonException
Code: 4
Message: Syntax error
File: /var/www/docker-aio/php/src/ContainerDefinitionFetcher.php
Line: 59
Trace: #0 /var/www/docker-aio/php/src/ContainerDefinitionFetcher.php(59): json_decode('', true, 512, 4194304)
#1 /var/www/docker-aio/php/src/ContainerDefinitionFetcher.php(392): AIO\ContainerDefinitionFetcher->GetDefinition()
#2 /var/www/docker-aio/php/public/index.php(142): AIO\ContainerDefinitionFetcher->FetchDefinition()

I'm stopping my test here, please let me know if this is fixed and has been tested.

[pabzm]

(see previous comment)

[szaimen]

@pabzm this is ready for review now 😊

[szaimen]

@pabzm for testing best to compile the container from this branch locally and then testing it out. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-locally-build-and-test-changes-to-mastercontainer

[pabzm]

Technically this mostly works now, great!

There's more problem left, which is that caddy apparently can't get a certificate for the dyn hostname. It responds with status code 502, and writes this to the container log:

{"level":"error","ts":1782206806.7762344,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"my-nextcloud.dedyn.io","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:dns - DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-nextcloud.dedyn.io - check that a DNS record exists for this domain"}
{"level":"error","ts":1782206806.7764018,"logger":"tls.obtain","msg":"will retry","error":"[my-nextcloud.dedyn.io] Obtain: [my-nextcloud.dedyn.io] solving challenge: my-nextcloud.dedyn.io: [my-nextcloud.dedyn.io] authorization failed: HTTP 400 urn:ietf:params:acme:error:dns - DNS problem: NXDOMAIN looking up TXT for _acme-challenge.my-nextcloud.dedyn.io - check that a DNS record exists for this domain (ca=https://acme-v02.api.letsencrypt.org/directory)","attempt":1,"retrying_in":60,"elapsed":12.806447381,"max_duration":2592000}

When checking manually via their web interface, desec.io also does not show this DNS record.

Additionally I'd like to raise two UX issues

1. This caution text irritates me:

I (as a user) didn't chose to run dnsmasq and now I'm told that it's going to be a problem. Also this sounds like I would need to turn it off. But how? (And isn't dnsmasq actually a requirement for this desec setup?)

2. I'd suggest to use a different icon for warnings (as the first item is one, as far as I undertand) and notices. Or use the same prefix word, if both are warnings.

3. Somewhere early before registering we should make it very clear that this only works if the server has a public IP address, or has certain ports forwarded to it.

[pabzm]

Thanks for debugging the certificate issues!

Here's my suggestion for the changed wording.

[szaimen]

Thanks for debugging the certificate issues!

Here's my suggestion for the changed wording.

Thanks a lot!

Adjusted :)

[pabzm]

Looks good to me! Very nice feature! 🎉

[pabzm]

🚀