suprexus
suprexus
Same here. Work around for me was to change permissions of the letsencrypt/live directory on the host itself. sudo chmod -R 775 letsencrypt_dir/live Survives container restarts after that.
Check your path - /live doesn't seem correct. Check your docker config to see where you're saving the letsencrypt files. sudo chmod -R 775 letsencrypt_dir/live
Gotcha - What user owns the directory? If you're specifying a PUID in your docker compose file, it should be the same user.
I didn't change the symlinks - What I probably did do was change the permissions on the entire npm directory to include the ../../archive/. Try recreating the symlinks and chmod...
What permissions are set on ../../archive/npm-1/ ls -la archive/npm-1/ are you running the container as a certain user?