I just received my Nextbox and started to configure the remote access via Guided Dynamic DNS. Which works well, the Nextcloud instance is reachable via the registered URL at deSEC.
But automatic activation of HTTPS/TLS fails with the message “Failed to acquire my.subdomain.dedyn.io with email@example.com” (details in error message changed for priv. reasons).
Do you have any hint why the acquisition of the LetsEncryp TLS certificate fails?
Do you have a subdomain in the form of: “my.subdomain.dedyn.io” set up? Currently only a simple subdomain is supported (without 2 dots before .dedyn.io) … something like: “mysubdomain.dedyn.io” ?
Acquiring a certificate mostly fails if letsencrypt cannot reach your NextBox.
- Are you sure ports 80 and 443 are open towards the right client on your router?
- You can access your Nextcloud instance via the public URL (best case from outside your LAN - try mobile without wifi) ?
- Does the domain correctly resolve to your IPv4 and IPv6 address? (this might be relevant due to DS-Lite internet connections, which do not allow incoming traffic through IPv4)
If this does not help, please write firstname.lastname@example.org and refer to this post, there we can support you better by also exchanging none public information.
thanks for the hint with the additional sub-domain, that solved the problem.