Hey, yes I did use acme.sh.
I assume you have already done the
acme.sh --issue
part. This drops the certificate and private key files within~/.acme.sh/example.com/
(substitute your domain). For example, in there you’ll findfullchain.cer
andexample.com.cer
, and you’ll usually use the former.
That's the thing I can't find anything of the sort only what I've listed in my OP.
mydomain.com.conf
mydomain.com.csr
mydomain.com.csr.conf
mydomain.com.key
If you can find the
.csr
file but you can’t find thefullchain.cer
file in that directory, it means that acme.sh did not issue a certificate - it failed and you’ll need to look at the previous output ofacme.sh --issue
to identify why.
I issued the certificate it via nginx and it appears it did work because another one of my subdomains has https, but when I look into the folder like you mentioned it has the same structure of items that I previously listed. I think it creates it automatically, but if you want it to add it to a service manually then this falls apart.