I’m afraid I can’t help you without knowing what operations were performed in the background. You’ll have to get in touch with whoever wrote that integration.
Hi Peter,
how about a logical consideration?
For my current domain, I make my settings in two places in the router: Port sharing and DynDNS. This works since years. Accordingly, the letsencrypt commands in nextcloudpi must be OK.
Assuming that I can set the port shares correctly, my inputs to DynDNS are the critical point.
I received the details after registering with deSEC and copied into keepassx.
So first I would like to check the defaults at deSEC. Is it possible?
alwi