Nginx uses self-signed certificate instead of Let’s Encrypt one

Hello Using Nginx for the first time. On CentOS 7.5.

Used https://certbot.eff.org/lets-encrypt/centosrhel7-nginx.html

Then after the issue https://www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/

Have pem files in /etc/letsencrypt/live.

Created a conf file in /etc/nginx/conf.d. CertBot has not modified it.

Have “[alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)” after running “sudo nginx -t && nginx -s reload” Does not seem to be SELinux issue.

No nginx configuration file issue.
error log only had “2018/11/19 16:11:38 [notice] 32498#0: signal process started.”

Where to look next?

3 Replies

Used http://nginx.org/en/docs/http/configuring_https_servers.html to manually configure nginx.
Set the /etc/nginx/conf.d/servername.conf file to be:

server {
listen 443 default_server;
listen [::]:443 default_server;
root /var/www/html;
server_name servername;
ssl_certificate /path/to/fullchain.pem;
ssl_certificate_key /path/to/privkey.pem;
ssl_protocols TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
}

Restarted nginx. Browsers still only see the self-signed cert.

Have not seen anything helpful in:

/var/log/messages
/var/log/nginx/error.log, access.log
/var/log/letsencrypt/letsencrypt.log

No way found to correct the error. VM deleted.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct