Attempt to Renew SSL Cert

Help
21

Well, that seems to explain the need for separate certs.
It doesn't explain how/why more that one cert is trying to use the same cert name.

1 Like
22

seriously?

1 Like
23

Try:
lsb_release -a
cat /etc/os-release
cat /etc/issue

1 Like
24

I smell bitnami stink.

1 Like
25

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
root@ip-172-31-74-110:~# ^C

26

I thought LiteSpeed

$ curl -Ii http://acuzen.com/.well-known/acme-challenge/sometestfile
HTTP/1.1 404 Not Found
Date: Thu, 17 Aug 2023 20:58:17 GMT
Server: LiteSpeed
Connection: Keep-Alive
1 Like
27

Now, can you follow the certbot installation/upgrade instructions?

1 Like
28

Yeah, pretty uncommon and definitely not bitnami. I hope.

2 Likes
29

I can follow cut and paste text
:person_gesturing_ok:

30

Certbot Instructions | Certbot (eff.org)
Formatting might be a bit off:

  1. SSH into the serverSSH into the server running your HTTP website as a user with sudo privileges.
  2. Install snapdYou'll need to install snapd and make sure you follow any instructions to enable classic snap support.Follow these instructions on snapcraft's site to install snapd.

install snapd

  1. Remove certbot-auto and any Certbot OS packagesIf you have any Certbot packages installed using an OS package manager like apt, dnf, or yum, you should remove them before installing the Certbot snap to ensure that when you run the command certbot the snap is used rather than the installation from your OS package manager. The exact command to do this depends on your OS, but common examples are sudo apt-get remove certbot, sudo dnf remove certbot, or sudo yum remove certbot.
  2. Install CertbotRun this command on the command line on the machine to install Certbot.

sudo snap install --classic certbot

  1. Prepare the Certbot commandExecute the following instruction on the command line on the machine to ensure that the certbot command can be run.

sudo ln -s /snap/bin/certbot /usr/bin/certbot

  1. Choose how you'd like to run Certbot

Either get and install your certificates...

Run this command to get a certificate and have Certbot edit your apache configuration automatically to serve it, turning on HTTPS access in a single step.

sudo certbot --apache

Or, just get a certificate

If you're feeling more conservative and would like to make the changes to your apache configuration by hand, run this command.

sudo certbot certonly --apache

  1. Test automatic renewalThe Certbot packages on your system come with a cron job or systemd timer that will renew your certificates automatically before they expire. You will not need to run Certbot again, unless you change your configuration. You can test automatic renewal for your certificates by running this command:

sudo certbot renew --dry-run

The command to renew certbot is installed in one of the following locations:

  • /etc/crontab/
  • /etc/cron.*/*
  • systemctl list-timers
  1. Confirm that Certbot workedTo confirm that your site is set up properly, visit https://yourwebsite.com/ in your browser and look for the lock icon in the URL bar.
3 Likes
31

I did notice that you had previously used "--webroot".
If using "--apache" fails, then you can always use "--webroot".

Please do all testing on the LE staging environment - not LE production system.

3 Likes
32

That probably warrants a --deploy-hook "systemctl reload $SOMETHING" too.

4 Likes
33

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.