No certificates found

Help
21

I think that only the later ones are numbered. I think the original ones aren't. I could be wrong though. We'll find out from update_symlinks. :grin:

3 Likes
22

@griffin You're wrong :stuck_out_tongue:

4 Likes
23

If update_symlinks can't find them then I'm wrong. :stuck_out_tongue:

3 Likes
24

root@nc-jail:~ # certbot update_symlinks
Saving debug log to /var/log/letsencrypt/letsencrypt.log
root@nc-jail:~ # certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

No certificates found.

root@nc-jail:~ #

3 Likes
25

Even if update_symlinks works, I've helped someone recently where certbot would give a Python error due to the fact someone manually messed with the /archive/ folder because of the missing number suffix.

Could you give us the output of:

ls -l /usr/local/etc/letsencrypt/live/cloud.lemovstudio.com/

?

4 Likes
26

sudo ls -la /usr/local/etc/letsencrypt/live/cloud.lemovstudio.com/

3 Likes
27

Great minds think alike! :upside_down_face:

3 Likes
28

root@nc-jail:~ # ls -la /usr/local/etc/letsencrypt/live/cloud.lemovstudio.com/
total 6
drwxr-xr-x 2 root wheel 3 Mar 24 18:52 .
drwxr-xr-x 3 root wheel 3 Mar 24 15:50 ..
---------- 1 root wheel 692 Mar 24 15:51 README
root@nc-jail:~ #

3 Likes
29

update_symlinks probably requires a functional renewal configuration file.

Let's do it manually. First we rename the files with the number suffix, then we make the symlinks:

rename ".pem" "1.pem"  /usr/local/etc/letsencrypt/archive/cloud.lemovstudio.com/*
cd  /usr/local/etc/letsencrypt/live/cloud.lemovstudio.com/
ln -s ../../cert1.pem cert.pem
ln -s ../../chain1.pem chain.pem
ln -s ../../fullchain1.pem fullchain.pem
ln -s ../../privkey1.pem privkey.pem

Now test certbot please, you probably need to use --config-dir /usr/local/etc/letsencrypt

5 Likes
30

Yep. Need to try renaming them with 1's after each.

2 Likes
31

That's certainly possible. Probably easier just to grab new certs.

3 Likes
32

@giuseppe30

What webserver you using? Apache, nginx?

3 Likes
33

I use ngix :stuck_out_tongue:

3 Likes
34

try this:

sudo certbot certonly --nginx -d "cloud.lemovstudio.com" --dry-run

I think your port 80 is timing out though.

4 Likes
35

I've typed some instructions above worth trying first :slight_smile:

6 Likes
36

Didn't see those.

@giuseppe30

Try Osiris's method first.

5 Likes
37

Edit took some time :slight_smile: You guys were quick with the new replies :wink:

4 Likes
38

ok go slow pls :stuck_out_tongue:

4 Likes
39

These are the instructions:

5 Likes
40

test with this:

certbot certificates --config-dir /usr/local/etc/letsencrypt

@Osiris

I'm hoping the config-dir parameter isn't actually needed. That's gonna become super annoying.

3 Likes