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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
This is a community support forum, meaning most people here helping are volunteering their time and expertise. Helping to spread the support load across the community is why this works. Please elaborate on the issues you’re encountering, so that the community can assist.
I think we already have an account but obviously no credentials, we have an OVH account referencing a cert from letsencrypt, we have no access to root on ovh, but access to CP and no access to the original cert
I’m thinking of giving up on ovh / letsencrypt and repointing DNS and recreating the site and a proper cert
And it’s also not limited to one cert per domain (although there are rate limits, there can definitely be several valid certificates for the same names at the same time). So there’s really nothing to stop just starting over in this kind of situation.