Certificate reliability

[kapdome]

I HAD SOME SSL ISSUE AND FINALY DISCOVER THAT LE CERTS RIGHT NOW ASSESSED NON RELIABLE, In R3, WHAT I HAVE TO CONSIDERE THERE ALWAYS FREE ? MAY I NEED A NSW PLAN TO AUTHENTICATES MY WEB SERVICES ?

LET ME NOW WHAT IS THE PLAN, I AM ABLE TO GENERATE R3 NON RELIABLE WITH CERTBOT, MAYBE I HAVE TO CHANGE FOR BOULDER ?

LET US KNOW WHAT IS THE RIGHT PROCESSUS, BEST REGARDS, SINCERLY YOURS, IN THE RESPECT OF YOUR AMAZING PROJEC
My domain is:

I ran this command: kapdome.com fatsendclear.com

It produced this output:
only the non reliability of R3 certificate

My web server is (include version):
nginx ... (to update)

The operating system my web server runs on is (include version):
ubuntu

My hosting provider, if applicable, is:
ovh

I can login to a root shell on my machine (yes or no, or I don't know):
yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

certbot 2.1.0

[petercooperjr]

It's hard for me to understand what you're asking, which may be a language difference of some sort. Looking at your post history, you've had challenges in the past with your site not being available to all parts of the Internet all the time, which means that Let's Encrypt can't validate you actually own your name. I don't know if that's the "reliability" you're talking about. But if so, it's really not a Let's Encrypt issue (and you may find the same challenges using some other CA) or anything to do with the R3 intermediate, it's just that in order for a web site to work it needs to be available for people to connect to.

Let's Encrypt's servers have a pretty good track record of being reliable, though they aren't up 100% of the time just like anybody else isn't. I'm not sure what kind of advice you're exactly looking for.