cannot load certificate "/etc/letsencrypt/live/example.tld/fullchain.pem It's trying to load a certificate on a path that maybe doesn't exists. replace "example" with your domain name in the conf...
It's trying to load a certificate on a path that maybe doesn't exists. replace "example" with your domain name in the conf file. If it's already been done, and you still gets this error, it means nginx is loading another file, possibly in the same directory, that contains the error.
I guess you already installed letsenscrypt and generated your ssl keys properly.
What I would do is cd /etc/nginx/sites-enabled/ grep -Hrn 'example' * Check the result(s) in prompt and then edit the file(s). sudo nano the files, update the text and save the file with ctrl-x/ Y...
What I would do is
cd /etc/nginx/sites-enabled/
grep -Hrn 'example' *
Check the result(s) in prompt and then edit the file(s).
sudo nano the files, update the text and save the file with ctrl-x/ Y enter
if you still get the error after that, I would check if there is another directory which nginx may use.
Check in the /etc/nginx/nginx.conf file for a include statement. Something like :
Within the relevant /etc/nginx/.../pleroma.conf file be sure to scroll all the way down in the file... Because i have found that sometimes the let's encrypt certbot adds an additional, extraneous...
Within the relevant /etc/nginx/.../pleroma.conf file be sure to scroll all the way down in the file... Because i have found that sometimes the let's encrypt certbot adds an additional, extraneous couple of lines for the "/etc/letsencrypt/live/example.tld/fullchain.pem" snippets. Of course i think the error might be different, but never hurts to double-check.
Separately, when i used to run pleroma, of all the little cuts in setting it up or upgrading it, the nginx portion was fine for me...its the other stuff that annoyed me...at least a few years ago (so could have been early days). Good luck!
cannot load certificate "/etc/letsencrypt/live/example.tld/fullchain.pem
It's trying to load a certificate on a path that maybe doesn't exists. replace "example" with your domain name in the conf file. If it's already been done, and you still gets this error, it means nginx is loading another file, possibly in the same directory, that contains the error.
I guess you already installed letsenscrypt and generated your ssl keys properly.
What I would do is
cd /etc/nginx/sites-enabled/
grep -Hrn 'example' *
Check the result(s) in prompt and then edit the file(s).
sudo nano the files, update the text and save the file with ctrl-x/ Y enter
if you still get the error after that, I would check if there is another directory which nginx may use.
Check in the /etc/nginx/nginx.conf file for a include statement. Something like :
include /etc/nginx/conf.d/*.conf;
Hope this helps
It’s probably in the file mentioned in the next line - try a
grepto check if this is true.Within the relevant /etc/nginx/.../pleroma.conf file be sure to scroll all the way down in the file... Because i have found that sometimes the let's encrypt certbot adds an additional, extraneous couple of lines for the "/etc/letsencrypt/live/example.tld/fullchain.pem" snippets. Of course i think the error might be different, but never hurts to double-check.
Separately, when i used to run pleroma, of all the little cuts in setting it up or upgrading it, the nginx portion was fine for me...its the other stuff that annoyed me...at least a few years ago (so could have been early days). Good luck!