Hello.
I tried to get a certificate for my PBS following the documentation but have found many problems.
Now it seems that I finally made it by using certbot.
However, despite having received the certificate, HTTPS does not work when visiting my PBS from a browser.
As read above, certbot says my certificate and key are saved at
If I go to my server this is what I see at the location mentioned by the documentation:
And this is what I see at the location mentioned by certbot:
If things weren't confusing enough, they are symbolic links!
Which take here:
What should I do?
I would be very grateful if anyone could please help me to have a working certificate : )
Cheers
I tried to get a certificate for my PBS following the documentation but have found many problems.
Now it seems that I finally made it by using certbot.
Code:
root@pbs:~# certbot certonly --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --preferred-challenges dns --debug-challenges -d \*.pbs.mydomain.com -d pbs.mydomain.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for *.pbs.mydomain.com and pbs.mydomain.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Challenges loaded. Press continue to submit to CA.
Pass "-v" for more info about challenges.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/pbs.mydomain.com/fullchain.pem
Key is saved at: /etc/letsencrypt/live/pbs.mydomain.com/privkey.pem
This certificate expires on 2025-07-07.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.However, despite having received the certificate, HTTPS does not work when visiting my PBS from a browser.
As read above, certbot says my certificate and key are saved at
/etc/letsencrypt/live/pbs.mydomain.com/ while the documentation shows a different location and different names ("proxy").If I go to my server this is what I see at the location mentioned by the documentation:
Code:
root@pbs:~# ls -hal /etc/proxmox-backup/
total 42K
drwx------ 2 backup backup 11 Apr 9 08:06 .
drwxr-xr-x 84 root root 167 Apr 8 22:16 ..
-rw-rw---- 1 backup backup 0 Apr 8 17:32 .domains.lck
-rw------- 1 root root 119 Jan 27 18:49 authkey.key
-rw-r----- 1 root backup 113 Jan 27 18:49 authkey.pub
-rw-r----- 1 root backup 86 Jan 27 18:49 csrf.key
-rw-r----- 1 root backup 142 Apr 9 08:06 domains.cfg
-rw-r----- 1 root backup 3.2K Jan 27 18:49 proxy.key
-rw-r----- 1 root backup 2.1K Jan 27 18:49 proxy.pem
-rw-rw---- 1 backup backup 0 Mar 16 23:06 tfa.json.lock
-rw-r----- 1 root backup 38 Jan 27 18:45 user.cfgAnd this is what I see at the location mentioned by certbot:
Code:
root@pbs:~# ls -hal /etc/letsencrypt/live/pbs.mydomain.com/
total 16K
drwxr-xr-x 2 root root 7 Apr 8 22:33 .
drwx------ 3 root root 4 Apr 8 22:33 ..
-rw-r--r-- 1 root root 692 Apr 8 22:33 README
lrwxrwxrwx 1 root root 41 Apr 8 22:33 cert.pem -> ../../archive/pbs.mydomain.com/cert1.pem
lrwxrwxrwx 1 root root 42 Apr 8 22:33 chain.pem -> ../../archive/pbs.mydomain.com/chain1.pem
lrwxrwxrwx 1 root root 46 Apr 8 22:33 fullchain.pem -> ../../archive/pbs.mydomain.com/fullchain1.pem
lrwxrwxrwx 1 root root 44 Apr 8 22:33 privkey.pem -> ../../archive/pbs.mydomain.com/privkey1.pemIf things weren't confusing enough, they are symbolic links!
Which take here:
Code:
root@pbs:~# ls -hal /etc/letsencrypt/archive/pbs.mydomain.com/
total 19K
drwxr-xr-x 2 root root 6 Apr 8 22:33 .
drwx------ 3 root root 3 Apr 8 22:33 ..
-rw-r--r-- 1 root root 1.4K Apr 8 22:33 cert1.pem
-rw-r--r-- 1 root root 1.6K Apr 8 22:33 chain1.pem
-rw-r--r-- 1 root root 2.9K Apr 8 22:33 fullchain1.pem
-rw------- 1 root root 241 Apr 8 22:33 privkey1.pemWhat should I do?
I would be very grateful if anyone could please help me to have a working certificate : )
Cheers
