Error ERR_SSL_UNRECOGNIZED_NAME_ALERT I've been down for two days. Please help

I followed the below instructable to apply SSL to the site. Lets Encrypt

This procedure indicated some errors:

For example:

maquino@codigobyte:/etc/nginx/sites-enabled$ sudo nginx -t

nginx: [warn] conflicting server name "" on, ignored
nginx: [warn] conflicting server name "" on, ignored
nginx: [warn] conflicting server name "" on [::]:80, ignored
nginx: [warn] conflicting server name "" on [::]:80, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

The issue is that my site is down, I’m already on the third day and Digital Ocean support tells me that they don’t see a problem in the configurations. But the site is down.

On the next page it shows me a problem with the secure connection.

At this moment there are several things that make me believe that I have a problem in the following configuration:

In /etc/nginx/sites-enabled$

I have 3 files and one of them is my site


server {
    listen 80;
    listen [::]:80;
    server_name todocontenidoweb;
    server_tokens off;
    root /home/forge/;

In the server_name line all web content; I understand that I should put www.todocontenidos

But it doesn’t allow me and it gives me an error in the certificate if I do this.

I would really appreciate it if someone could help me to solve this situation.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.


Is it possible to send us your 3 config files, so we can check what’s wrong ?

Thank you.

Bobby Iliev
Site Moderator
Site Moderator badge
July 23, 2022

Hi there,

As far as I can see from the Nginx warnings, you have your domain defined in two different Nginx server blocks. You would need to remove the duplicate Nginx server block and then try to re-issue your certificate.

You can find which server blocks the domain name is defined in using the grep command:

grep /etc/nginx/sites-enabled/

Once you know the specific files, delete the duplicate one using the rm command, restart nginx with systemctl restart nginx and then run the certbot command form the tutorial again.



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up