i wasn’t using the free universal edge cert, lost track of it and couldn’t figure out how to download it again, because there isn’t any link on Cloudflare to do that, so i deleted it with the hope of creating a new one.
now the curl -x patch fix isn’t working, despite giving a success message:
More? --data “{"certificate_authority":"digicert"}”
{“result”:{“enabled”:true,“certificate_authority”:“digicert”},“success”:true,“errors”:,“messages”:}
You shouldn’t need to download the Edge Certificate.
Cloudflare will automatically use the Edge Certificate certificate when serving (proxied ) requests. You may be thinking of an Origin Certificate (which you should install on your origin server)?
i think that it started because i got the free edge cert mixed up with imported ssl certs for the paid plans, which can be deleted, then yeah i got it confused with the origin cert.
i toggled it in the dashboard, so far it’s not coming back.
The Let’s Encrypt that user4358 is referring to there is still automatic: Cloudflare will generate a Let’s Encrypt certificate for you (instead of Digicert).
that tip does work on the base url, thx for posting it.
the subdomain.domain however is not secure, but i never tried that before, and it might also be a dns issue.
the previous api post was giving “unmatched close/brace bracket” errors, but this works, although some of the slashes aren’t transferring over to this post:
What subdomain? Universal SSL certificates should cover example.com and *.example.com so all one-level subdomains should be good to go. Multi-level subdomains like a.b.example.com won’t work with Universal SSL certificates. They can be accommodated by Advanced Certificate Manager – not every possible subdomain because multi-wildcards like ..example.com still aren’t allowed but wildcards like .b.example.com or a..example.com can be added.