Website only opens with www, no support when www is omitted

Help
23

Might need to specify an installer plugin

certbot --apache

TWO dashes :face_with_raised_eyebrow:

11 Likes
24

I ran the below command :slight_smile:
certbot certonly

Here is the below output, please which option would be appropriate for my corrections.

Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):
25

I wouldn't suggest certony in this case

certbot --apache
9 Likes
26

Running certbot with the flag --apache made the below output :slight_smile:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
The requested apache plugin does not appear to be installed
27

EDIT: How did you install certbot originally via snap? or apt?

9 Likes
28

The output from certbot-apache :slight_smile:

install: missing destination file operand after 'certbot-apache'
Try 'install --help' for more information.
29

Hang on lets slow down a bit so we don't have to rinse and repeat!

9 Likes
30

I now have the below from dumping the vhost :slight_smile:

VirtualHost configuration:
*:443                  www.adaoma.shop (/etc/apache2/sites-enabled/adaoma.shop-le-ssl.conf:2)
*:80                   is a NameVirtualHost
         default server ip-172-31-21-87.us-west-1.compute.internal (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost ip-172-31-21-87.us-west-1.compute.internal (/etc/apache2/sites-enabled/000-default.conf:1)
         port 80 namevhost adaoma.shop (/etc/apache2/sites-enabled/adaoma.shop.conf:1)
                 alias www.adaoma.shop
         port 80 namevhost adaoma.shop (/etc/apache2/sites-enabled/adaoma.shop.conf:18)
                 alias www.adaoma.shop
2 Likes
31

please show the entire command string you used to install the plugin...

sudo apt install certbot-apache ???

(IF apt was used to install certbot initally)
We are very close. No "running by the pool"

10 Likes
32

sudo apt install certbot-apache

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package certbot-apache
2 Likes
33

OK please hang for a minute.
Made a mistake

9 Likes
34

I still see two vhosts.

Also, what happened to the Amazon cert [which included the wildcard entry]?:

image
image765×417 59.1 KB

10 Likes
35

Im not getting the plugin right.
Gonna hold back for a couple minutes because I don't know how certbot was actually installed

10 Likes
36

We should check what LE cert(s) are left.
Please show:
certbot certificates

10 Likes
37

Please be patient, am at the middle of the night here, I made the necessary changes without restarting Apache before I was cut short of electrical power supply, will restart Apache when it's day break and the changes should reflect. :smile:

3 Likes
38

Here too - LOL

10:42 PM

11 Likes
39

@lordmalcolm No problem.
Sun is going down here ;0)
7:42PM

11 Likes
40

[3:45am] Will do that when it's day break here, am chatting from my phone now. :smile:
I deeply appreciate all your responses, well educating.

4 Likes
41

Thinking about the current situation and how to best go forward...
I think we should use --webroot authentication; As certbot may get confused by the (redirection and) lack of FQDN coverage - the HTTPS vhost only covers "www" and we will be requesting a cert with both names.
OR
Go certonly and make the cert change manually in the HTTPS vhost config.

11 Likes
42

I concur. Either way.
@lordmalcolm was able to get and configure a cert for www. the apache plugin is likely to complicate matters unnecessarily

11 Likes