Open cmmarslender opened 7 years ago
I'm trying to figure this one out too... It looks like the TXT records never make it to the zone
Any news on this?
We have the exact same problem, wich occured when adding new subdomains to our list.
I'm experiencing the same problem
I'm experiencing the same problem
Did you copy paste my response? lol
I'm experiencing the same problem
I think this problem is specific to Cloudflare (though it may not be Cloudflare's fault).
The issue seems to resolve itself when I toggle the cloud icon on the failing CNAME/A record.
@willseward toggle from what state to what? I'm having the same problem.
Is there a way to manually set the token to return via TXT record?
I don't know if it helps, but in my case, I had a CNAME record that was pointing to the root domain. After I have changed it not to point root, but to point the same server as root – everything went just fine and did it smoothly.
@z3cka I toggled it on for the certificate issuance, and then off because I don't require it.
@kimaero Yes, I had exactly the same situation. In my experience, it would transiently place the TXT records on the target of the CNAME instead of the correct domain. When I removed the CNAME it stopped happening, but started again soon after.
Thanks for the response! I ended up using the HTTP method rather than the DNS based challenge and it worked like a charm.
Cheers!
Same thing here, using Cloudflare had a CNAME with the subdmain I wanted www
in that case pointing to the root, and I started getting this error.
Removed the subdomain CNAME and it worked
Not sure if this is a problem with cloudflare, or just a more general problem. This used to work fine, and only recently stopped working.
Trying to issue a certificate for root domain and www.domain.com, and am getting errors over and over. Here is the log from the container: