I'm attempting to set up a standalone secure certificate using CertBot and create a symbolic link (
./public/certbot) from my server so that I can include the certificates without them actually being under the directory tree of the server (this is a Linode I use for testing and development, so I'm going to be using a variety of server software). The certificates have installed successfully under
/etc/letsencrypt/, and as instructed in the CertBot documentation, installation was done using
sudo, so all the files are owned by root. I have tried everything I could think of to create a symlink that the server can read, but I keep getting a permission error. Currently, the symlink file,
/etc/letsencrypt/live, the domain folder, and all files inside the domain folder have been
sudo chmodded to
777, and I tried creating the symlink file without
sudo, but it didn't let me. As a normal user, I am able to
cd into the symlink file and
ls the domain folder without
sudo, so I can see everything in there, but when I start my server (currently
webpack-dev-server), it doesn't have permission. The error message from the server indicates that the path is being resolved correctly (since it's giving me an access error, not
I've also tried creating a real
public/certbot folder and individual symlinks to the certificate files, with the same errors.
There must be some gap in my knowledge about Linux permissions. Is there a way around this? Thanks.