Mounting the letsencrypt "live" folder for upstream server

Task:

We are using a reverse proxy for an upstream server on a separate VMs.

Both have the same DNS name.

I’d like to know how to mount the letsencrypt “live” folder on the upstream server so i can share the pem files.

The problem is that the “live” folder is a symlink to the “archive” older and in the “archive” folder the pem files are named .pem2, .pem3, etc.

Until i find a solution i will continue to manually move and rename the .pem files.

Thanks

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:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

The /live/ symbolic link will always point to the latest cert files.
You should not try to go directly to the /archive/ folder.

You could always nfs mount the /etc/letsencrypt directory on your secondary server, this would let the symbolic links work correctly as they are ‘relative’ links
EG: cert.pem -> ../../archive/hostname.net.au/cert3.pem

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.