Issue with Dynv6 can't find Zone token mismatch

Ok, hi sorry for the delay but got it fixed, after wasting a couple with an AI, that basically rewrote the source code of ACME for me, till I simply solved the issue by deleting all single dedicated permission code tokens in Dynv6 and then generate only one with all permission, that handles then ddclient, and ACME (wich i use now for cert.). Which solved the second Zone not being found issue, instead of having two token handeling ddclient and one for all, to give the certificate permission. And I exported the token full number key to ACME, instead of name I gave to the key. Oh yea, and by giving my server blocks the same Name as my webside Domain of cause. Website is online and certified works now... Again thanks a lot guys! :blush:

Maybe sido.com entry could be an
leftover from the time my site was offline...?