Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It seems that your wildcard request failed because they require a DNS TXT record to be created and you had a TYPO in that entry [missing the leading underscore].
The subsequent "workaround" (trying to obtain a non-wildcard cert) likely only worked because that did NOT require a DNS change and used HTTP authentication instead.
Note: Although it is a valid solution to this problem, you should "learn" why the previous request failed.
[In the event that you should ever require a wildcard cert, you will be better prepared to get one.]
we actually tried both versions and neither of them worked, so finally had to apply the workaround and then we were able to edit it to make it a wildcard
Something worked.
I suppose it was when using HTTP authentication.
As for the DNS authentication, you need to ensure all authoritative DNS servers are in sync and return the proper TXT record before proceeding with that request.
yeah i dont know how it worked, but can you help me with the following issue -
Please help, our domain is getting redirected to www.https//www.ezmethods.com, and hence, our site is not loading, we have checked our code but could not find any issues, we have also checked server settings and found no problem.