When you renew your certificate, you usually have to install it to install it to your webserver and reload your webserver for it to take effect.
Since that hasn’t happened, please answer every question below so we can give you relevant advice.
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:rinex.org.rw
I ran this command:certbot certificates
It produced this output:getting these error:Found the following certs:
Certificate Name: rinex.org.rw
Domains: rinex.org.rw www.rinex.org.rw
Expiry Date: 2019-08-21 13:30:43+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/rinex.org.rw/fullchain.pem
Private Key Path: /etc/letsencrypt/live/rinex.org.rw/privkey.pem
My web server is (include version): Apache/2.4.7 (Ubuntu)
The operating system my web server runs on is (include version):Ubuntu 14.04.5 LTS
My hosting provider, if applicable, is: i have access to the server.
I can login to a root shell on my machine (yes or no, or I don’t know):
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):certbot 0.31.0
the issue i have the certficate renewed in backend but it does applied to the browser.
hello am getting these response:/etc/apache2/sites-enabled/rinex.org.rw-le-ssl.conf:SSLCertificateFile /etc/letsencrypt/live/rinex.org.rw/cert.pem
/etc/apache2/sites-available/rinex.org.rw-le-ssl.conf:SSLCertificateFile /etc/letsencrypt/live/rinex.org.rw/cert.pem
these are my virtualhost:
<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly. #ServerNamewww.example.com
ServerAdmin noc@ricta.org.rw
ServerName rinex.org.rw
ServerAlias www.rinex.org.rw
DocumentRoot /var/www/rinex.org.rw/public_html
#Redirect permanent / https://rinex.org.rw/
<Directory /var/www/rinex.org.rw/public_html/>
Options FollowSymLinks
AllowOverride All
Require all granted
</Directory>
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/rinex.error.log
CustomLog ${APACHE_LOG_DIR}/rinex.access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =rinex.org.rw
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw
#RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =rinex.org.rw
#RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
# RewriteEngine on
# RewriteCond %{SERVER_NAME} =rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw
# RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]
the is another folder created after letsencrypt installation:
cat rinex.org.rw-le-ssl.conf
<VirtualHost *:443>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly. #ServerNamewww.example.com
ServerAdmin noc@ricta.org.rw
ServerName rinex.org.rw
ServerAlias www.rinex.org.rw
DocumentRoot /var/www/rinex.org.rw/public_html
#Redirect permanent / https://rinex.org.rw/
<Directory /var/www/rinex.org.rw/public_html/>
Options FollowSymLinks
AllowOverride All
Require all granted
</Directory>
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/rinex.error.log
CustomLog ${APACHE_LOG_DIR}/rinex.access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =rinex.org.rw
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw
#RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =rinex.org.rw
#RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
# RewriteEngine on
# RewriteCond %{SERVER_NAME} =rinex.org.rw [OR]
#RewriteCond %{SERVER_NAME} =www.rinex.org.rw
# RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]
Srv Child Server number - generation
PID OS process ID
Acc Number of accesses this connection / this child / this slot
M Mode of operation
CPU CPU usage, number of seconds
SS Seconds since beginning of most recent request
Req Milliseconds required to process most recent request
Conn Kilobytes transferred this connection
Child Megabytes transferred this child
Slot Total megabytes transferred this slot
SSL/TLS Session Cache Status:
cache type: SHMCB, shared memory: 512000 bytes, current entries: 2
subcaches: 32, indexes per subcache: 88
time left on oldest entries’ objects: avg: 245 seconds, (range: 244…246)
index usage: 0%, cache usage: 0%
total entries stored since starting: 20
total entries replaced since starting: 0
total entries expired since starting: 13
total (pre-expiry) entries scrolled out of the cache: 0
total retrieves since starting: 12 hit, 20 miss
total removes since starting: 0 hit, 0 miss
i created new apache and installed new certificates but it doesn’t applied on the browser .
what vhost am i using cause the one am using is this rinex.org.rw-le-ssl.conf (file created after letsencrypt installation).
and these one in sites-available: rinex.org.rw.conf