Home > Blockchain >  ERR_SSL_UNRECOGNIZED_NAME_ALERT Nginx
ERR_SSL_UNRECOGNIZED_NAME_ALERT Nginx

Time:05-10

I was using Laravel Forge and stopped using it due to a problem with my card. So I continued on my own with Digital Ocean.

I followed the below instructable to apply SSL to the site. enter image description here

//End of Edit

There seems to an issue with your nginx config. It seems like your config is only allowing port 80 and not 443. Browsers expect to get 443 as port (unless you otherwise specify) as ssl port. And it seems like you're using some redirect to redirect users from http to https, only problem is you're not running any https service on port 443.

I could be an issue with your nginx config. make sure that the server entry that has the ssl input, also running on port 443.

If you did install ssl with let's encrypt, you can try to generate certificate manually and then you can modify nginx config to run on port 443 as ssl

You can follow this guide from digitalocean , just replace the certificates path with lets-encrypt one

Edit 2 :

I don't think this part should be commented out

    # FORGE SSL (DO NOT REMOVE!)
    # ssl_certificate;
    # ssl_certificate_key;

    # ssl_protocols TLSv1.2 TLSv1.3;
    # ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY13>
    # ssl_prefer_server_ciphers off;
    # ssl_dhparam /etc/nginx/dhparams.pem;

As you're essentially not serving any ssl certificate through the 443 port.

Here is an example server from DigitalOcean. As you can see, they're serving a private and public key. Once you generate your certificate, you need to enter the path of those.

server {
    listen 443 http2 ssl;
    listen [::]:443 http2 ssl;

    server_name your_server_ip;

    ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt;
    ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key;
    ssl_dhparam /etc/ssl/certs/dhparam.pem;
}

End of Edit

  • Related