Hi all, first off what a bloody brilliant tool this is. I tip my hat to the deves.
Now I am moving of IIS to nginx, and have got my test site up and running forcing all traffic to HTTPs. However my API will not load now over HTTPs as its only HTTP. How can I allow http to this one end point of localhost:3000. My conf is for nginx is here: https://dpaste.org/Zx2E
That I can do easily. Can I use the same cert generated by certdog for the api that sits on the same domain or should I create a new one using the CLI for .com/api
On the left side of your screenshot, you can see that the node service is running as the user fishpal+ - the + indicates that the name has been truncated for the output. It seems fairly likely that the node service is running as the fishpaladmin user (the one youâre logged-in as).
As @schoen said, by default the certificate tree is only readable by ârootâ. Definitely do NOT add fishpaladmin to root. However, it might be appropriate in your case for certbot to use a --deploy-hook action to provide a copy of the certificate chain with appropriate fishpaladmin-accessible permissions to a node directory.
Yep! Thereâs even an example deploy-hook if you scroll down in that link I posted, so you might be able to adjust it to your system without much problem.
So I got my bash script running with my renewal process. Will drop it into the appropriate folder for auto run later. My issue is the files are not actually appearing in the expected folder.
No errors are produced from what i can see so far.
Hi @JuergenAuer, still having trouble getting this to work. Are you sure I can use the same certs on my api as when I do the below on the server itself, you see the error as well as 404 when browsing directly
curl -i -H "Accept: application/json" -H "Content-Type: application/json" https://127.0.0.1:3000/api/status
curl: (51) SSL: no alternative certificate subject name matches target host name '127.0.0.1'