Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
t.mcmotor.ps
I ran this command:
sudo certbot --nginx -d t.mcmotor.ps
It produced this output:
My web server is (include version):
nginx/1.14.0
The operating system my web server runs on is (include version):
ububtu 18.04
My hosting provider, if applicable, is:
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):
0.31.0
In addition nginx config file as follow
server {
listen 0.0.0.0:80;
listen 0.0.0.0:443 ssl default;
server_name t.mcmotor.ps;
access_log /var/log/nginx/autoapp_t_access.log;
error_log /var/log/nginx/autoapp_t_error.log;
access_log /var/log/nginx/auto_t_debug.log;
gzip on;
gzip_min_length 1000;
gzip_comp_level 9;
#gzip_proxied expired no-cache no-store private auth;
gzip_proxied any;
gzip_types text/plain application/json;
location / {
root /var/www/autoapp_t;
index index.html index.htm;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/t.mcmotor.ps/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/t.mcmotor.ps/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
}