Hello,
After succesfully moving a test web server to HTTPS, I performed the same task on a real server.
While Firefox is happy, Chrome still says it's "Not secure".
FWIW, the site uses no cookies, and I told nginx to reload its configuration file.
Any idea what it could be?
Thanks for any help.
~# certbot --nginx -d www.acme.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for www.acme.com
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/www.acme.com/fullchain.pem
Key is saved at: /etc/letsencrypt/live/www.acme.com/privkey.pem
This certificate expires on 2026-04-08.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
Deploying certificate
Successfully deployed certificate for www.acme.com to /etc/nginx/sites-enabled/default
Congratulations! You have successfully enabled HTTPS on https://www.acme.com
~# cat /etc/nginx/sites-available/default
# Default server configuration
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}
server {
root /usr/share/nginx/acme;
index index.html index.htm;
server_name www.acme.com acme.com;
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/www.acme.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/www.acme.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = www.acme.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name www.acme.com acme.com;
listen 80;
return 404; # managed by Certbot
}