Here are some snippets from the Nginx config. I wasn’t sure what you meant by what version so I’m hoping this helps.
plex.conf
root /var/www/plex-certbot-webroot;
....
#Use letsencrypt.org to get a free and trusted ssl certificate
ssl_certificate /etc/letsencrypt/live/plex.jcconnell.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/plex.jcconnell.com/privkey.pem;
...
location /.well-known {
root /var/www/ssl-proof/plex/;
}
couchpotato.conf
root /var/www/couchpotato-certbot-webroot;
# The public and private parts of the certificate are linked here
ssl_certificate /etc/letsencrypt/live/couchpotato.jcconnell.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/couchpotato.jcconnell.com/privkey.pem;
location /.well-known {
root /var/www/ssl-proof/couchpotato/;
}
It seems to me that @sahsanu helped someone in a similar situation in this thread:
Can you understand the effects of these commands and how they would apply to your situation? If so, you could try this approach to change the destination of the symlinks.
If you don’t understand what this is doing, I can try to offer more specific advice.
@sahsanu’s advice at the beginning to make a backup is also very appropriate.
Thank you for that link, I followed the directions for both domains after creating a backup. It seems both domains are still rate limited so it might be a few days before I know it’s it’s successful.
I ran the original and the new one in a diff tool and nothing immediately stood out to me. I’m trying to better understand everything here. Could you tell me what you see that makes you optimistic?
First, there are no lineages mentioned with -0001 names (so everything has been consolidated in the right direction), and second, it can still parse all of the PEM files, which means that the links in live point to files that actually exist.
Thanks again! I’ll keep an eye on the certificates and follow-up here in a week or so. I believe this coming Saturday, 10/28 is when a new Plex certificate may be issued.
