I’m trying to switch from connecting my NexBox via nextbox.link to connecting it via dedyn.io, mostly because the former way is really slow.
The first steps go fine : in the ‘Guided DNS configuration’, I created my .dedyn address successfully and then get a page that says:
HTTPS / TLS Configuration
Successfully resolved: [myservername].dedyn.io to: [myIP]
Failed resolving: [myservername].dedyn.io [IPv6] need: (…) found: null
Successfully tested reachability for: [myservername].dedyn.io
HTTPS / TLS is not activated
→ Enable HTTPS
From this, I understand (maybe wrongly) that my dedyn redirection is working well; also I checked sending and receiving mails on the NextBox’s Nextcloud.
Now, my router (Turris) is too complex for me to set up the DNS-Rebind (I thought it was not a catastrophy for now)
But that’s where things become interesting : when I click ‘Enable HTTPS’, after a while I get a message that says : 'failed to acquire [myserver]dedy.io with [the mail I declared for the admin user]'
while AT THE SAME TIME I am actually connected via https on the .nextbox.link instance (the page is https://[myservername].nextbox.link/apps/nextbox/#)
So there is something I don’t understand here. Why can I access in https through .nextbox.link and at the same time the interface tells me it doesn’t work?
I suspect this is related to the wrong rebinding, because when I try [myservername].dedyn.io I land on my router interface front-end, so it does not route the request to the NextBox…
But do I understand correctly that the https step ha gone OK, in spite of the negative message I get?