Did not create a certificate for www

Help
#1

My domain is: smarthomeliving.org

I ran this command: sudo certbot --apache

It produced this output: certificate created

My web server is (include version):Debian 9 stretch

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Google Cloud

I can login to a root shell on my machine (yes or no, or I don't know):yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No SSH

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

I created a certificate for smarthomeliving.org but I did not create a cert for www.smarthomeliving.org

2 Likes
#2

Hi @charveyjr,

The names suggested by certbot --apache depend on the names on your existing Apache VirtualHosts in your existing Apache configuration. If you don't have a ServerAlias for the www version of the name, Certbot won't realize that you would need that alias on your certificate.

If you add the appropriate ServerAlias to the relevant VirtualHost and then run Certbot again, you should be able to get a certificate for both names.

3 Likes
#3

Perhaps your wordpress also needs to understand that the site has two names (one with and one without the www).

  1. http domain returns with:
    HTTP/1.1 301 Moved Permanently - Location: https://smarthomeliving.org/
    <p>The document has moved <a href="https://smarthomeliving.org/">here</a>.</p>

  2. http www.domain returns with:
    lots of content - a web page

  3. https domain returns with:
    lots of content - a secure web page

  4. https www.domain returns with:
    SSL ERROR - www name not in cert used.
    But if you ignore the error message and continue...
    You get lots of content - a insecure/secure web page

#1 is OK (redirects to #3)
#2 should redirect to HTTPS #4
#3 is where you want all to go - as this is the only GOOD and working secure site
#4 should redirect to #3 - but first needs its' name included in the cert

To fully correct this, you will need:

  1. a cert with both names on it.
    but that depends on the wordpress/apache configuration (as noted by @schoen)
  2. proper redirection - you need to decide which will be the main site (with or without the www) and redirect the other three to that one.
2 Likes
#4

I am working in Google Cloud. Do i need to remove certbot and then reinstall?

Or is there a file within SSH I need to change?

2 Likes
#5

The site shows WordPress.
I would assume you can make the changes within that.

image
image719×456 71.8 KB

2 Likes
#6

I was assuming you would edit your Apache configuration files with a text editor (accessed over SSH) because that's the classic way of configuring Apache if you're using the command line to administer a server. But if WordPress is able to make equivalent configuration changes for you somehow, as @rg305 suggests, that sounds great.

2 Likes
#7

Thanks

I went to /var/www/html/ and I looked at index.php and wp_config.php. There was nothing in these files that looked like where I add my www web address.

2 Likes
#8

How do you manage/configure your Apache? I.e., how did you install your Wordpress site?

Also, could you paste the output of apachectl -S ?

2 Likes
#9

I manage Apache though the SSH in the Google Cloud Console..

Installed wordpress through the Google Cloud implementation.

$ apachectl -S
-bash: apachectl: command not found

1 Like
#10

Hmm, you're not using the Bitnami software stack by any chance?

2 Likes
#11

No, I had a hard time working with Bitnami

1 Like
#12

Execute the command as root or use sudo.

1 Like
#13

sudo apachectl -S
VirtualHost configuration:
*:443 smarthomeliving.org (/etc/apache2/sites-enabled/000-default-le-ssl.conf:2)
*:80 smarthome-1-vm.us-central1-f.c.smarthomeliving.internal (/etc/apache2/sites-enabled/000-default.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="www-data" id=33
Group: name="www-data" id=33

1 Like
#14

That seems to be lacking:

  1. The port 80 vhost config for SmartHomeLiving.org
  2. The www ServerAlias for both 80 and 443

Seeing that the 443 is using the same named file (with -le-ssl), it would indicate that the name "SmartHomeLiving.org" did appear in that port 80 vhost config at the time LE was run.
Since then things have been changed (but have not made things better).

You need to have a working port 80 vhost config for both names.
You need to get a cert with both names on it.
[you can check which cert names you have covered now with: cerbot certificates]
You need to redirect three of the four sites to the one final destination.
Then you need to check that the renewals are functional with:
certbot renew --dry-run

Then you will certainly have a Happy New Year!
Cheers from Miami :beers:

#15

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