Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a website serving several pages that can be reachable via HTTP.

How can I make these sites available via standard HTTPS? (not self-signed). What are the steps? (go to a CA, and then?)

Can someone please describe the full process in steps?

share|improve this question

closed as too broad by Jeff Schaller, Anthon, don_crissti, Thomas Dickey, cuonglm Jun 20 at 12:11

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

This probably belongs on serverfault.com – bitmask Jan 27 '12 at 15:01
@bitmask I'd say superuser.com – Karlson Jan 27 '12 at 15:16
I'm having trouble deciding if this is on-topic. I think it'll mostly be Apache configuration stuff, which is – Michael Mrozek Jan 27 '12 at 15:22
Not superuser. Since the process to accomplish this is OS-agnostic, it would probably go on serverfault, even if the commands are Unix/Linux. – Kevin M Jan 27 '12 at 15:24
@MichaelMrozek: my personal opinion is: too broad. To be answered correctly, you'd need to explain the steps to create the right type of key-pair and CSR (not Unix/Linux-specific), explain what sort of documents CAs expect in addition to the CSR (could vary widely by CA/country/jurisdiction, not Unix/linux-related either). Then you need to go through the whole apache setup, including virtual hosts, algorithm selection/restriction, redirects maybe, ... which is again (mainly) OS agnostic. I don't think it would stay open at serverfault. – Mat Jan 27 '12 at 17:00

There are many tutorials for apache on how to do this. This is one of them.

Here is another one

One thing that you would change if you already have a certificate generated you would copy the certificate files to appropriate locations vs. generating them yourself.

If you are not using apache please post the webserver you're using.

share|improve this answer
i am using apache – LanceBaynes Jan 27 '12 at 14:41
@LanceBaynes I modified the answer to fit your case better. – Karlson Jan 27 '12 at 14:45

While this question is a year old, many CA will provide tools and tutorials to help with this. See RapidSSL - their knowledgebase covers pretty much all common setups.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.