You should see something very similar to this:lrwxrwxrwx 1 root root 43 Dec 16 17:08 cert.pem -> ../../archive/test.firstdomain.co.uk/cert1.pemlrwxrwxrwx 1 root root 44 Dec 16 17:08 chain.pem -> ../../archive/test.firstdomain.co.uk/chain1.pemlrwxrwxrwx 1 root root 48 Dec 16 17:08 fullchain.pem -> ../../archive/test.firstdomain.co.uk/fullchain1.pemlrwxrwxrwx 1 root root 46 Dec 16 17:08 privkey.pem -> ../../archive/test.firstdomain.co.uk/privkey1.pem
If you do not see these files, stop. Troubleshoot the problem before proceeding. If you continue, you will break your web server any anything else that depends on SSL. If you do see these files, go ahead and configure SME with the certificates generated:config setprop modSSL crt /etc/letsencrypt/live/test.firstdomain.co.uk/cert.pemconfig setprop modSSL key /etc/letsencrypt/live/test.firstdomain.co.uk/privkey.pemconfig setprop modSSL CertificateChainFile /etc/letsencrypt/live/test.firstdomain.co.uk/chain.pemsignal-event domain-modify; signal-event email-update; signal-event ibay-modify
Question , is what / where does the fullchain.pem file value fit into the config setprop modSSL .... ?