2024-07-16, 08:46 PM
Actually, the creation of the cert was not quite that straightforward. My ISP blocks port 80, so the standard letsencrypt/certbot mechanism does not work.
I had to use certbot at the command line to create the cert, and (as prompted by certbot) I had to temporarily create a TXT record on my DNS service to allow this to work. Once that was done, I attempted to create the cert again in NPM (same domain name) and it seemed to 'find' the one I had created at the command line. Now the cert looks OK in NPM and I can successfully request its renewal there. So I think it's good but its creation was a bit strange.
I had to use certbot at the command line to create the cert, and (as prompted by certbot) I had to temporarily create a TXT record on my DNS service to allow this to work. Once that was done, I attempted to create the cert again in NPM (same domain name) and it seemed to 'find' the one I had created at the command line. Now the cert looks OK in NPM and I can successfully request its renewal there. So I think it's good but its creation was a bit strange.