Same server, different Apache virtual hosts, second- and third-level domains

[ratnaji]

Hi there

I am afraid this must be in a FAQ. I have just joined Letsencrypt and very much beginner. This is what I need to do:

• I deliver different web sites from the same server, Debian LAMP, using Apache virtual hosts. So typically I have all sorts of *.conf files in /etc/apache2/sites-available belonging to the different sites.
• Some sites are third level domains. eg. http://www.example.com.
• And I have a different set of sites in the format http://example.net/foo, http://example.net/bar, etc.

Right now everything runs fine with HTTP. I want to promote all of them to HTTPS. Does Lets encrypt allow that? If so, could you point me to the instructions?

[JuergenAuer]

Hi @ratnaji

@ratnaji

• I deliver different web sites from the same server, Debian LAMP, using Apache virtual hosts. So typically I have all sorts of *.conf files in /etc/apache2/sites-available belonging to the different sites.
• Some sites are third level domains. eg. http://www.example.com.
• And I have a different set of sites in the format http://example.net/foo, http://example.net/bar, etc.

that's the standard configuration most users have.

Read the basics

How It Works - Let's Encrypt

then select a client.

ACME Client Implementations - Let's Encrypt

[ratnaji]

Hi Juergen
Thanks for providing the links! I am used to manually copy the certificates to the server and make them available to httpd. The concept of Let’s Encrypt surprised me.

Yep, it works though. I have already enabled SSL in two web sites, one with the second level domain and one with a third level doman.

[JuergenAuer]

@ratnaji

I am used to manually copy the certificates to the server and make them available to httpd.

The main concept of Letsencrypt is "Automation". Certificates are only 90 days valid, so you have to do that every 60 - 85 day.

Having a lot of domains that doesn't work.