Certificate Expiration does not match

bryllej8 · November 4, 2019, 4:47am

[root@mail letsencrypt]# more /opt/zimbra/conf/nginx.conf

NGINX POP/IMAP proxy configuration file for use with Zimbra

working_directory /opt/zimbra;
include /opt/zimbra/conf/nginx/includes/nginx.conf.main;
include /opt/zimbra/conf/nginx/includes/nginx.conf.memcache;
include /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup;
include /opt/zimbra/conf/nginx/includes/nginx.conf.mail;
include /opt/zimbra/conf/nginx/includes/nginx.conf.web;

Don't edit the below comment

#SUCCESS

rg305 · November 4, 2019, 4:48am

more /opt/zimbra/conf/nginx/includes/nginx.conf.web

bryllej8 · November 4, 2019, 4:50am

[root@mail letsencrypt]# more /opt/zimbra/conf/nginx/includes/nginx.conf.web
http
{
# disable nginx version on error pages
server_tokens off;

upstream_fair_shm_size 32k;

root /opt/zimbra/data/nginx/html;

# You need to customize these two values by setting local config
# proxy_server_names_hash_max_size and proxy_names_hash_bucket_size
# when too many virtual host names are added
server_names_hash_max_size 512;
server_names_hash_bucket_size 64;

# Define whether nginx will match exact server version against the
# version received in the client request. Defaults to 'on'
# Setting this to off will make nginx compare only the major and minor
# server versions (eg. all 8.5.x will be treated same by nginx)
exact_version_check on;

# Define the collection of upstream HTTP webclient servers to which we will proxy
# Define each server:port against a server directive
#
upstream zimbra_webclient
{
    server    mail.cebucity.gov.ph:8080 fail_timeout=10s version=8.8.15_GA_3829;

    zmauth;
}

#  Define the collection of upstream HTTP servers to which we will proxy
#  Define each server:port against a server directive
#
upstream zimbra
{
    server    mail.cebucity.gov.ph:8080 fail_timeout=10s version=8.8.15_GA_3829;

    zmauth;
}

#  Define the collection of upstream HTTPS webclient servers to which we will proxy
#  Define each server:port against a server directive

rg305 · November 4, 2019, 4:51am

more /opt/zimbra/conf/nginx/includes/nginx.conf.web.https
more /opt/zimbra/conf/nginx/includes/nginx.conf.web.https.default

bryllej8 · November 4, 2019, 4:52am

[root@mail letsencrypt]# more /opt/zimbra/conf/nginx/includes/nginx.conf.web.https
[root@mail letsencrypt]# more /opt/zimbra/conf/nginx/includes/nginx.conf.web.https.default

HTTPS Proxy Default Configuration

Strict servername enforcing block

Enabled/disabled through the ‘zimbraReverseProxyStrictServerName’ configuration item

The ${listen.:addresses} is NOT demarcated with web.strict.servername on purpose.

#server {

#listen [::]:443 default_server ipv6only=off;

listen 443 default_server;

#listen [::]:443 default_server;

server_name _;

# Listen addresses extracted from `zimbraVirtualIPAddress` on each domain

ssl on;

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

ssl_prefer_server_ciphers on;

ssl_session_cache shared:SSL:10m;

ssl_session_timeout 600;

ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA2

56:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECD
SA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE
-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128:AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4;

ssl_ecdh_curve prime256v1;

ssl_certificate /opt/zimbra/conf/nginx.crt;

ssl_certificate_key /opt/zimbra/conf/nginx.key;

ssl_verify_client off;

ssl_verify_depth 10;

ssl_dhparam /opt/zimbra/conf/dhparam.pem;

return 400;

#}

server
{
#listen [::]:443 ipv6only=off;
listen 443;
#listen [::]:443;

server_name             mail.cebucity.gov.ph; # add aliases and perhaps public
client_max_body_size    0;

rg305 · November 4, 2019, 4:57am

    ssl_certificate         /opt/zimbra/conf/nginx.crt;
    ssl_certificate_key     /opt/zimbra/conf/nginx.key;

It might be a simple as replacing that with:

ssl_certificate         /etc/letsencrypt/live/mail.cebucity.gov.ph/fullchain.pem
ssl_certificate_key     /etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem

But ZIMBRA seems to want to do things in its’ own ways…

rg305 · November 4, 2019, 5:05am

The documented method is more like:

su zimbra
/opt/zimbra/bin/zmcertmgr verifycrt comm /etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem /etc/letsencrypt/live/mail.cebucity.gov.ph/cert.pem
[if that is OK - success]
cp /etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem /opt/zimbra/ssl/zimbra/commercial/commercial.key
/opt/zimbra/bin/zmcertmgr deploycrt comm /etc/letsencrypt/live/mail.cebucity.gov.ph/cert.pem /etc/letsencrypt/live/mail.cebucity.gov.ph/chain.pem
zmcontrol restart
exit

bryllej8 · November 4, 2019, 5:08am

you mean fullchain.pem copied and paste to nginx.crt ?
privkey.pem to nginx.key ?

rg305 · November 4, 2019, 5:11am

yes.
If you want to try that, backup the current files first.
replace them and restart zimbra

su zimbra
zmcontrol restart
zmcontrol status
- if anything failing
zmcontrol start
- if still failing
replace files with backups and restart zimbra and try the other method

bryllej8 · November 4, 2019, 5:14am

[zimbra@mail ~]$ cd /opt/zimbra/ssl/letsencrypt/

[zimbra@mail letsencrypt]$ /opt/zimbra/bin/zmcertmgr verifycrt comm /etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem /etc/letsencrypt/live/mail.cebucity.gov.ph/cert.pem
** Verifying '/etc/letsencrypt/live/mail.cebucity.gov.ph/cert.pem' against '/etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem'
ERROR: Can't read file '/etc/letsencrypt/live/mail.cebucity.gov.ph/privkey.pem'
ERROR: Can't read file '/etc/letsencrypt/live/mail.cebucity.gov.ph/cert.pem'

[zimbra@mail letsencrypt]$ /opt/zimbra/bin/zmcertmgr verifycrt comm privkey.pem cert.pem chain.pem
** Verifying 'cert.pem' against 'privkey.pem'
Certificate 'cert.pem' and private key 'privkey.pem' match.
** Verifying 'cert.pem' against 'chain.pem'
Valid certificate chain: cert.pem: OK

i tried your command but its not working and i tried the code from zimbra documentation

source: Installing a LetsEncrypt SSL Certificate - Zimbra :: Tech Center

rg305 · November 4, 2019, 5:21am

I assumed the file name:
ls -l /etc/letsencrypt/live/

bryllej8 · November 4, 2019, 5:23am

im currently here and tried to restart the zimbra hope this works

finger cross

rg305 · November 4, 2019, 5:26am

Please show:
ls -l /etc/letsencrypt/live/

bryllej8 · November 4, 2019, 5:26am

[root@mail ~]# ls -l /etc/letsencrypt/live/
total 4
-rw-r–r--. 1 root root 740 Aug 7 04:28 README
drwxr-xr-x. 2 root root 93 Nov 3 22:44 mail.cebucity.gov.ph

rg305 · November 4, 2019, 5:28am

It must be a permissions problem - the files are there.
show files with:
ls -l /etc/letsencrypt/live/mail.cebucity.gov.ph/
Zimbra user has no right to read them.

rg305 · November 4, 2019, 5:30am

Cert expiration hasn’t changed:

bryllej8 · November 4, 2019, 5:32am

yes, thats correct.

so i think i will try the nginx.crt etc... i guess

bryllej8 · November 4, 2019, 5:33am

sadly yes

rg305 · November 4, 2019, 5:34am

if that fails, copy the needed files to another location (like: /opt/zimbra/cert - create path)
then make those files readable by zimbra or all
let zimbra use them then delete them

rg305 · November 4, 2019, 5:35am

zimbra cert integration needs a little love

If you only have the one zimbra server that may work.
If you have more (and they operate together) that may fail as zimbra needs to update itself in local ldap for server to server communications.

Topic		Replies	Views
Certificate renewal email doesn't match certificates? Help	4	996	December 23, 2021
I received a message from letsencrypt on: aug 30 2022 with Your certificate (or certificates) for the names listed below will expire in 9 days (on 09 Sep 22 12:48 +0000). Please make sure to renew your certificate before then, or visitors to your web site Help	3	700	September 30, 2022
Renew fail. expire date in broser is wrong Help	10	1957	May 18, 2018
Certificate Installed & Valid & Working. But certbot certificates shows the expired cert Help	12	1670	November 12, 2021
Certbot: "Certificates" command shows different expiry dates than OpenSSL Help	11	4879	May 26, 2018

Certificate Expiration does not match

NGINX POP/IMAP proxy configuration file for use with Zimbra

Don't edit the below comment

HTTPS Proxy Default Configuration

Strict servername enforcing block

Enabled/disabled through the ‘zimbraReverseProxyStrictServerName’ configuration item

The ${listen.:addresses} is NOT demarcated with web.strict.servername on purpose.

#listen [::]:443 default_server ipv6only=off;

listen 443 default_server;

#listen [::]:443 default_server;

server_name _;

# Listen addresses extracted from zimbraVirtualIPAddress on each domain

# Listen addresses extracted from zimbraVirtualIPAddress on each domain

ssl on;

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

ssl_prefer_server_ciphers on;

ssl_session_cache shared:SSL:10m;

ssl_session_timeout 600;

ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA2

ssl_ecdh_curve prime256v1;

ssl_certificate /opt/zimbra/conf/nginx.crt;

ssl_certificate_key /opt/zimbra/conf/nginx.key;

ssl_verify_client off;

ssl_verify_depth 10;

ssl_dhparam /opt/zimbra/conf/dhparam.pem;

return 400;

Related topics

# Listen addresses extracted from `zimbraVirtualIPAddress` on each domain

# Listen addresses extracted from `zimbraVirtualIPAddress` on each domain