NET::ERR_CERT_AUTHORITY_INVALID nginx

[JonathanMtz]

I’m new administrating a server, now i’m trying to access to my domain but Chrome, safari, etc. respond with a this error: NET::ERR_CERT_AUTHORITY_INVALID

My domain is: tododetodobellezaysalud.com/

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

My hosting provider, if applicable, is: DigitalOcean

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): No

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

[rg305]

Welcome to the LE community

EDIT - that was incorrect.

Can you show the exact message you get?
[screenshot if possible]

[JonathanMtz]

I guess i just solved it by adding this line

to my /etc/nginx/sites-available/tododetodobellezaysalud.com file
If it wasn’t that i don’t know what happened.

[JuergenAuer]

Hi @JonathanMtz

@JonathanMtz

I’m new administrating a server, now i’m trying to access to my domain but Chrome, safari, etc. respond with a this error: NET::ERR_CERT_AUTHORITY_INVALID

My domain is: tododetodobellezaysalud.com

I don't see a problem. Your certificate is valid

CN=tododetodobellezaysalud.com
	13.01.2019
	13.04.2019
expires in 31 days	tododetodobellezaysalud.com, 
www.tododetodobellezaysalud.com - 2 entries

and you have a Grade C, both https - connections are secure, two redirects http -> https. The only thing - you don't have a preferred version, instead two https results with http status 200.

And Ssllabs is happy - Grade A:

SSL Server Test (Powered by Qualys SSL Labs)

Recheck your domain in a few days if certbot has created a new certificate.

[_az]

@JonathanMtz

If it wasn’t that i don’t know what happened.

ssl_trusted_certificate would not have this effect.

Perhaps:

• Your nginx server did not get reloaded properly after certificate installation, and after a further reload/restart the certificate started being served, or
• You were checking from an old browser tab (some browsers tend to cache SSL verification errors), and the last time you tested it, you re-opened it.