Help needed with SSL installation/configuration

Hi Everyone,

In May (last month), we bought a Thawte SSL certificate for our domain (hosted on Linode), through our domain registrar.

I followed the instructions at: http://library.linode.com/security/ssl-certificates

titled "Securing Servers with SSL" to install the SSL certificate.

However, at some point in the configuration, we had to get some info from Thawte and the domain registrar to proceed further.

I did that, but there was confusing/conflicting instructions on the next steps to take from the domain registrar, Thawte and the write up on the Linode Library I was following

The result was that https wasn't working on the domain.

Now, I have to revisit the issue and solve it, hence I'm turning to the Linode community for help.

The files I have in /etc/ssl/certs/ (which really resolves to /etc/pki/tls/certs) are:

ca-bundle.crt

ca-bundle.trust.crt

makefile

make-dummy-cert

I would appreciate it greatly if someone could help spot what's wrong and how to fix it.

I will also readily provide any other info required to solve this problem/

Our Linode server runs CentOS 6.2 and Apache 2, with OpenSSL installed.

Thanks.

25 Replies

You normally need a certificate (public) and a private key (.pem/.key for example, can be other formats)

You have a couple of certificates now. You can read them with the following command to figure out which one is the one you need as public certificate:

openssl x509 -in filename.crt -noout -text

You do not have a private key however, at least.. None that I can see on the list… You should still have the private one somewhere. (Otherwise you need to request a new certificate all together :()

I'm not sure what's in the makefile, but you can see if it is related by just using cat on it to read it.

Thanks @Nuvini for your response.

Here's the mail I got from the domain registrar concerning the SSL certificate.

> Fw: [#MAT-411-5111]: SSL for mydomain.com


From: Stacy F. <sslsupport@mydomainregistrar.com>

Date: Fri, 11 May 2012 19:29:32 +0300

To: me

ReplyTo: sslsupport@mydomainregistrar.com

Subject: [#MAT-463-55374]: SSL for mydomain.com

Hello,

Please find your SSL certificate listed below:

–---BEGIN CERTIFICATE-----

MIIEODCCAyCgAwIBAgIQTarxF4sM0igkYG5sBXJbCTANBgkqhkiG9w0BAQUFADBe

MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMVGhhd3RlLCBJbmMuMR0wGwYDVQQLExRE

[ deleted text]

3oq9endpvJuOLHXxNQutL7pYqrWMVa/5j32NqD6Vs9afky45BmDeEm6+bg9cWpTc

RMjSywaTYwZ7VIkTAxPMEvqFaIWAiNoXLNa8E7ZZiXum7GOUgErp5xFSGwJtVDM1

hAAPuxlKVGx4vxT3ZGlrfJvho8u1mK18NnB0pw==

–---END CERTIFICATE-----

CA Bundle is listed below:

-----BEGIN CERTIFICATE-----

MIIEjzCCA3egAwIBAgIQdhASihe2grs6H50amjXAkjANBgkqhkiG9w0BAQUFADCB

qTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDHRoYXd0ZSwgSW5jLjEoMCYGA1UECxMf

[deleted text]

Le6/Wjv6iJx0bK8h3ZLswxXvlHUmRtamP79mSKod790n5rdRiTh9E4QMQPzQtfHg

2/lPL0ActI5HImG4TJbe8F8Rfk8R2exQRyIOxR3iZEnnaGNFOorZcfRe8W63FE0+

bxQe3FL+vN8MvSk/dvsRX2hoFQ==

–---END CERTIFICATE-----

-----BEGIN CERTIFICATE-----

MIIERTCCA66gAwIBAgIQM2VQCHmtc+IwueAdDX+skTANBgkqhkiG9w0BAQUFADCB

zjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ

[deleted text]

Cajd1FYVLnp5MV9jllMbNNkV6k9tcMq+9oKp7dqFd8x2HGqBCiHYQZl/Xi6Cweiq

95OBBaqStB+3msAHF/XLxrRMDtdW3HEgdDjWdMbWj2uvi42gbCkLYeA=

–---END CERTIFICATE-----

Please make sure to install certificate along with the CA Bundle to the server.

Please let us know if we may be of any further assistance.


Regards,

Stacy F.

Customer Support

and here are the contents of the Makefile

> [me@myserver certs]# cat Makefile

UTF8 := $(shell locale -c LC_CTYPE -k | grep -q charmap.*UTF-8 && echo -utf8)

SERIAL=0

.PHONY: usage

.SUFFIXES: .key .csr .crt .pem

.PRECIOUS: %.key %.csr %.crt %.pem

usage:

@echo "This makefile allows you to create:"

@echo " o public/private key pairs"

@echo " o SSL certificate signing requests (CSRs)"

@echo " o self-signed SSL test certificates"

@echo

@echo "To create a key pair, run \"make SOMETHING.key\"."

@echo "To create a CSR, run \"make SOMETHING.csr\"."

@echo "To create a test certificate, run \"make SOMETHING.crt\"."

@echo "To create a key and a test certificate in one file, run \"make SOMETHING.pem\"."

@echo

@echo "To create a key for use with Apache, run \"make genkey\"."

@echo "To create a CSR for use with Apache, run \"make certreq\"."

@echo "To create a test certificate for use with Apache, run \"make testcert\"."

@echo

@echo "To create a test certificate with serial number other than zero, add SERIAL=num"

@echo

@echo Examples:

@echo " make server.key"

@echo " make server.csr"

@echo " make server.crt"

@echo " make stunnel.pem"

@echo " make genkey"

@echo " make certreq"

@echo " make testcert"

@echo " make server.crt SERIAL=1"

@echo " make stunnel.pem SERIAL=2"

@echo " make testcert SERIAL=3"

%.pem:

umask 77 ; \

PEM1=/bin/mktemp /tmp/openssl.XXXXXX ; \

PEM2=/bin/mktemp /tmp/openssl.XXXXXX ; \

/usr/bin/openssl req $(UTF8) -newkey rsa:2048 -keyout $PEM1 -nodes -x509 -days 365 -out $PEM2 -set_serial $(SERIAL) ; \

cat $PEM1 > $@ ; \

echo "" >> $@ ; \

cat $PEM2 >> $@ ; \

$(RM) $PEM1 $PEM2

%.key:

umask 77 ; \

/usr/bin/openssl genrsa -aes128 2048 > $@

%.csr: %.key

umask 77 ; \

/usr/bin/openssl req $(UTF8) -new -key $^ -out $@

%.crt: %.key

umask 77 ; \

/usr/bin/openssl req $(UTF8) -new -key $^ -x509 -days 365 -out $@ -set_serial $(SERIAL)

TLSROOT=/etc/pki/tls

KEY=$(TLSROOT)/private/localhost.key

CSR=$(TLSROOT)/certs/localhost.csr

CRT=$(TLSROOT)/certs/localhost.crt

genkey: $(KEY)

certreq: $(CSR)

testcert: $(CRT)

$(CSR): $(KEY)

umask 77 ; \

/usr/bin/openssl req $(UTF8) -new -key $(KEY) -out $(CSR)

$(CRT): $(KEY)

umask 77 ; \

/usr/bin/openssl req $(UTF8) -new -key $(KEY) -x509 -days 365 -out $(CRT) -set_serial $(SERIAL)

[me@myserver certs]#

Do you think I still don't have a private key?

Thanks a lot.

Did Thawte also send you the makefile? It shouldn't be needed.

Basically when you created the CSR that you sent to Thawte for signing, you also used your private key. Using the guide you linked, it should be this step:

cd /etc/ssl/localcerts
openssl req -new -nodes -days 365 -keyout www.mydomain.com.key -out www.mydomain.com.csr

Where www.mydomain.com.key is the privatekey you need to include in the configuration, along with the certificates the e-mail contained. (The CA-Bundle and your own)

Thanks again @Nuvini

I remember typing that command…

Here's what I have:

[me@myserver ~]# cd /etc/httpd/ssl
[me@myserver ssl]# ls
mydomain_com.ca-bundle  www.mydomain.com.crt  www.mydomain.com.key
mydomain_com.crt        www.mydomain.com.csr

Are these files in the wrong place?

Thanks once again..

To get it to recognize the certificate you need to use these directives in the apache configuration (/etc/apache2/apache2.conf or the httpd.conf file)

SSLCertificateFile /etc/httpd/ssl/<crt file="">.crt # The one that contains "MIIEODCC" (from the e-mail you received)
SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com.key
SSLCACertificateFile /etc/httpd/ssl/mydomain_com.ca-bundle</crt> 

You might need to play around a bit with the exact file names since the ones in your latest post have slightly different names than the ones in your post earlier.

Hi @Nuvini

I'm stuck.

I included the lines in my virtual host declaration, but got:

Failed to start apache :
Starting httpd: Syntax error on line 1050 of /etc/httpd/conf/httpd.conf:
Invalid command 'SSLEngine', perhaps misspelled or defined by a module not included in the server configuration
[FAILED]

…and

[me@myserver /]# apachectl configtest
Syntax error on line 1048 of /etc/httpd/conf/httpd.conf:
Invalid command 'SSLCertificateFile', perhaps misspelled or defined by a module not included in the server configuration
[me@myserver /]# 

(when I commented out the SSLEngine directive)

Why are the SSL directives not being recognized?

I know I have mod_ssl installed as I had followed the instruction in the tutorial I had referenced earlier..

I had done..

yum install openssl
mkdir /etc/ssl/localcerts

Can you pls hep spot what's wrong here?

If it'll help, here's what my virtual host block looks like (and its similar to my other virtual host blocks- except for the SSL directives)

> # ServerAdmin webmaster@mydomain.com

DocumentRoot /var/www/vhosts/mydomain.com/httpdocs/

ServerName mydomain.com

ServerAlias www.mydomain.com

AllowOverride all

SSLEngine on

SSLCertificateFile /etc/httpd/ssl/www.mydomain.com.crt

SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com.key

SSLCACertificateFile /etc/httpd/ssl/mydomain_com.ca-bundle

SSLLogLevel warn

Very many thanks.

You need to uncomment:

"#"

Have you loaded the SSL module? I believe you have to include "LoadModule sslmodule modules/modssl.so" in the config.

Thanks @Nuvini

I just tried that now..

[me@myserver /]# apachectl configtest
httpd: Syntax error on line 216 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_ssl.so into server: /etc/httpd/modules/mod_ssl.so: cannot open shared object file: No such file or directory

I'm getting a new set of errors

:(

I just checked, there is no mod_ssl.so in the /etc/httpd/modules/ folder.

There are a whole lot of other mod* files in there, but no modssl

[me@myserver modules]# ls
libphp5.so              mod_cgid.so          mod_mime.so
mod_actions.so          mod_cgi.so           mod_negotiation.so
mod_alias.so            mod_dav_fs.so        mod_proxy_ajp.so
mod_asis.so             mod_dav.so           mod_proxy_balancer.so
mod_auth_basic.so       mod_dbd.so           mod_proxy_connect.so
mod_auth_digest.so      mod_deflate.so       mod_proxy_ftp.so
mod_authn_alias.so      mod_dir.so           mod_proxy_http.so
mod_authn_anon.so       mod_disk_cache.so    mod_proxy_scgi.so
mod_authn_dbd.so        mod_dumpio.so        mod_proxy.so
mod_authn_dbm.so        mod_env.so           mod_reqtimeout.so
mod_authn_default.so    mod_expires.so       mod_rewrite.so
mod_authn_file.so       mod_ext_filter.so    mod_setenvif.so
mod_authnz_ldap.so      mod_filter.so        mod_speling.so
mod_authz_dbm.so        mod_headers.so       mod_status.so
mod_authz_default.so    mod_ident.so         mod_substitute.so
mod_authz_groupfile.so  mod_include.so       mod_suexec.so
mod_authz_host.so       mod_info.so          mod_unique_id.so
mod_authz_owner.so      mod_ldap.so          mod_userdir.so
mod_authz_user.so       mod_log_config.so    mod_usertrack.so
mod_autoindex.so        mod_log_forensic.so  mod_version.so
mod_cache.so            mod_logio.so         mod_vhost_alias.so

How can I correct this?

I feel like Cap'n Obvious, but did you install the actual mod_ssl package?

Thanks @hawk7000

Yes, I did.

I just tried again, just to be sure and here's what I got:

[me@myserver modules]# yum install openssl
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: mirrors.coreix.net
 * epel: mirror01.th.ifl.net
 * extras: mirrors.coreix.net
 * updates: mirrors.coreix.net
66 packages excluded due to repository priority protections
Setting up Install Process
Package openssl-1.0.0-20.el6_2.5.i686 already installed and latest version
Nothing to do

or is there supposed to be another step I missed after installing openSSL?

Thanks @hawk7000

I really didn't know that.

So, I had modssl installed by doing : # yum install modssl

It installed successfully.

Then I I did this:

[me@myserver ssl]# apachectl configtest

[Tue Jun 26 10:19:13 2012] [warn] module ssl_module is already loaded, skipping

Syntax OK

[root@kuiperserver1 ssl]#

So thinking everything was OK, I went on to restart Apache, but got

Failed to start apache :
Starting httpd: [Tue Jun 26 10:19:41 2012] [warn] module ssl_module is already loaded, skipping
Apache/2.2.15 mod_ssl/2.2.15 (Pass Phrase Dialog)
Some of your private key files are encrypted for security reasons.
In order to read them you have to provide the pass phrases.

Server myserver:443 (RSA)
Enter pass phrase:Apache:mod_ssl:Error: Private key not found.
**Stopped
[FAILED]

Do you have an idea of what's wrong now?

Are you sure these files are correct and exist? Did you set up the permissions so that they are readable by the appropriate user?

Did you fill in the correct passphrase? Please verify that this one is correct. It probably cannot read it due to an incorrect passphrase.

SSLCertificateFile /etc/httpd/ssl/www.mydomain.com.crt

SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com.key

SSLCACertificateFile /etc/httpd/ssl/mydomain_com.ca-bundle

Pretty sure that you want SSLCertificateChainFile rather than SSLCACertificateFile, not that it's related to the immediate problem you are facing.

@Thanks @hawk7000

I have changed it to SSLCertificateChainFile

@Thanks Nuvini

I have changed the owner of the files to Apache (that's the user who needs to read the files, right?)

but the error persists.

How do I (re)enter the passphrase?

Many thanks for all your help guys..

@redhat19:

@Thanks @hawk7000

I have changed it to SSLCertificateChainFile

@Thanks Nuvini

I have changed the owner of the files to Apache (that's the user who needs to read the files, right?)

but the error persists.

How do I (re)enter the passphrase?

Many thanks for all your help guys..

Try this:

openssl rsa -in /etc/httpd/ssl/www.mydomain.com.key -out /etc/httpd/ssl/www.mydomain.com-noencryption.key

After that change the line to this:

SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com-noencryption.key

–----

If this fixes it we at least know the problem is with the private file being encrypted. Otherwise we can look elsewhere.

EDIT: And yes, the owner of the apache process has to be able to read the key. I work with debian so for me it is www-data, but I believe it is different for CentOS.

Thanks so much @Nuvini

I have carried out the steps here and everything else seems to work fine, except Apache does not start up.

Here's what I am getting:

Failed to start apache :
Starting httpd: [Tue Jun 26 12:47:54 2012] [warn] module ssl_module is already loaded, skipping
[FAILED]

While trying enter the phass phrase, here are the steps I went through (I didn't immediately remember what I had used as the pass phrase).

[me@mydomain /]# openssl rsa -in /etc/httpd/ssl/www.mydomain.com.key -out /etc/httpd/ssl/www.mydomain.com-noencryption.key
Enter pass phrase for /etc/httpd/ssl/www.mydomain.com.key:
unable to load Private Key
3077555948:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:evp_enc.c:535:
3077555948:error:0906A065:PEM routines:PEM_do_header:bad decrypt:pem_lib.c:476:
[me@mydomain /]# openssl rsa -in /etc/httpd/ssl/www.mydomain.com.key -out /etc/httpd/ssl/www.mydomain.com-noencryption.key
Enter pass phrase for /etc/httpd/ssl/www.mydomain.com.key:
unable to load Private Key
3078129388:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:evp_enc.c:535:
3078129388:error:0906A065:PEM routines:PEM_do_header:bad decrypt:pem_lib.c:476:
[me@mydomain /]# openssl rsa -in /etc/httpd/ssl/www.mydomain.com.key -out /etc/httpd/ssl/www.mydomain.com-noencryption.key
Enter pass phrase for /etc/httpd/ssl/www.mydomain.com.key:
writing RSA key
[me@mydomain /]# openssl rsa -in /etc/httpd/ssl/www.mydomain.com.key -out /etc/httpd/ssl/www.mydomain.com-noencryption.key
Enter pass phrase for /etc/httpd/ssl/www.mydomain.com.key:
writing RSA key
[me@mydomain /]# apachectl configtest
[Tue Jun 26 12:41:20 2012] [warn] module ssl_module is already loaded, skipping
Syntax OK

It now seems we're closer to the getting it working but something is still wrong..

Just so to help the troubleshooting, here's what my httpd.conf file looks like

#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <url:http: httpd.apache.org="" docs="" 2.2="">for detailed information.
# In particular, see
# <url:http: httpd.apache.org="" docs="" 2.2="" mod="" directives.html=""># for a discussion of each configuration directive.
#
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# The configuration directives are grouped into three basic sections:
#  1\. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2\. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3\. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/etc/httpd" will be interpreted by the
# server as "/etc/httpd/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# Don't give away too much information about all the subcomponents
# we are running.  Comment out this line if you don't mind remote sites
# finding out what major optional modules you are running
ServerTokens OS

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <url:http: httpd.apache.org="" docs="" 2.2="" mod="" mpm_common.html#lockfile="">);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/httpd"

#
# PidFile: The file in which the server should record its process
# identification number when it starts.  Note the PIDFILE variable in
# /etc/sysconfig/httpd must be set appropriately if this location is
# changed.
#
PidFile run/httpd.pid

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 60

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive Off

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

##
## Server-Pool Size Regulation (MPM specific)
## 

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# ServerLimit: maximum value for MaxClients for the lifetime of the server
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
 <ifmodule prefork.c="">StartServers       8
MinSpareServers    5
MaxSpareServers   20
ServerLimit      256
MaxClients       256
MaxRequestsPerChild  4000</ifmodule> 

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
 <ifmodule worker.c="">StartServers         4
MaxClients         300
MinSpareThreads     25
MaxSpareThreads     75 
ThreadsPerChild     25
MaxRequestsPerChild  0</ifmodule> 

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <virtualhost># directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_alias_module modules/mod_authn_alias.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule version_module modules/mod_version.so

#
# The following modules are not loaded by default:
#
#LoadModule asis_module modules/mod_asis.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule cgid_module modules/mod_cgid.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule ssl_module modules/mod_ssl.so
#

#
# Load config files from the config directory "/etc/httpd/conf.d".
#
Include conf.d/*.conf

#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
#  . On SCO (ODT 3) use "User nouser" and "Group nogroup".
#  . On HPUX you may not be able to use shared memory as nobody, and the
#    suggested workaround is to create a user www and use that user.
#  NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
#  when the value of (unsigned)Group is above 60000; 
#  don't use Group #-1 on these systems!
#
User apache
Group apache

### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <virtualhost>definition.  These values also provide defaults for
# any <virtualhost>containers you may define later in the file.
#
# All of these directives may appear inside <virtualhost>containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin root@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work.  See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make 
# redirections work in a sensible way.
#
#ServerName www.example.com:80

#
# UseCanonicalName: Determines how Apache constructs self-referencing 
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client.  When set "On", Apache will use the value of the
# ServerName directive.
#
UseCanonicalName Off

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
 <directory>Options FollowSymLinks
    AllowOverride None</directory> 

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
 <directory "="" var="" www="" html"="">#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
    Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#   Options FileInfo AuthConfig Limit
#
    AllowOverride None

#
# Controls who can get stuff from this server.
#
    Order allow,deny
    Allow from all</directory> 

#
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
#
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid.  This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
#
# See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
#
 <ifmodule mod_userdir.c="">#
    # UserDir is disabled by default since it can confirm the presence
    # of a username on the system (depending on home directory
    # permissions).
    #
    UserDir disabled

    #
    # To enable requests to /~user/ to serve the user's public_html
    # directory, remove the "UserDir disabled" line above, and uncomment
    # the following line instead:
    # 
    #UserDir public_html</ifmodule> 

#
# Control access to UserDir directories.  The following is an example
# for a site where these directories are restricted to read-only.
#
# <directory home="" *="" public_html="">#    AllowOverride FileInfo AuthConfig Limit
#    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#    <limit get="" post="" options="">#        Order allow,deny
#        Allow from all
#</limit> 
#    <limitexcept get="" post="" options="">#        Order deny,allow
#        Deny from all
#</limitexcept> 
#</directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents.  The MultiViews Option can be used for the 
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var index.htm

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
 <files ~="" "^\.ht"="">Order allow,deny
    Deny from all
    Satisfy All</files> 

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
TypesConfig /etc/mime.types

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
 <ifmodule mod_mime_magic.c="">#   MIMEMagicFile /usr/share/magic.mime
    MIMEMagicFile conf/magic</ifmodule> 

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted 
# filesystems.  On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs/2.2/mod/core.html#enablemmap
#
#EnableMMAP off

#
# EnableSendfile: Control whether the sendfile kernel support is 
# used to deliver files (assuming that the OS supports it). 
# The default is on; turn this off if you serve from NFS-mounted 
# filesystems.  Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#enablesendfile
#
#EnableSendfile off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <virtualhost># container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <virtualhost># container, that host's errors will be logged there and not here.
#
ErrorLog logs/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# "combinedio" includes actual counts of actual bytes received (%I) and sent (%O); this
# requires the mod_logio module to be loaded.
#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <virtualhost># container, they will be logged here.  Contrariwise, if you *do*
# define per- <virtualhost>access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog logs/access_log common

#
# If you would like to have separate agent and referer logfiles, uncomment
# the following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

#
# For a single logfile with access, agent, and referer information
# (Combined Logfile Format), use the following directive:
#
CustomLog logs/access_log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of:  On | Off | EMail
#
ServerSignature On

#
# Aliases: Add here as many aliases as you need (with no limit). The format is 
# Alias fakename realname
#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL.  So "/icons" isn't aliased in this
# example, only "/icons/".  If the fakename is slash-terminated, then the 
# realname must also be slash terminated, and if the fakename omits the 
# trailing slash, the realname must also omit it.
#
# We include the /icons/ alias for FancyIndexed directory listings.  If you
# do not use FancyIndexing, you may comment this out.
#
Alias /icons/ "/var/www/icons/"

 <directory "="" var="" www="" icons"="">Options Indexes MultiViews FollowSymLinks
    AllowOverride None
    Order allow,deny
    Allow from all</directory> 

#
# WebDAV module configuration section.
# 
 <ifmodule mod_dav_fs.c=""># Location of the WebDAV lock database.
    DAVLockDB /var/lib/dav/lockdb</ifmodule> 

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
 <directory "="" var="" www="" cgi-bin"="">AllowOverride None
    Options None
    Order allow,deny
    Allow from all</directory> 

#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Directives controlling the display of server-generated directory listings.
#

#
# IndexOptions: Controls the appearance of server-generated directory
# listings.
#
IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable Charset=UTF-8

#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions.  These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif

#
# AddDescription allows you to place a short description after a file in
# server-generated indexes.  These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz

#
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
#
# HeaderName is the name of a file which should be prepended to
# directory indexes. 
ReadmeName README.html
HeaderName HEADER.html

#
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing.  Shell-style wildcarding is permitted.
#
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

#
# DefaultLanguage and AddLanguage allows you to specify the language of 
# a document. You can then use content negotiation to give a browser a 
# file in a language the user can understand.
#
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will 
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
#
# * It is generally better to not mark a page as 
# * being a certain language than marking it with the wrong
# * language!
#
# DefaultLanguage nl
#
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
#
# Note 2: The example entries below illustrate that in some cases 
# the two character 'Language' abbreviation is not identical to 
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
#
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
#
# Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
# English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
# Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
# Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
# Norwegian (no) - Polish (pl) - Portugese (pt)
# Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
# Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
#
AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw

#
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW

#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
#
ForceLanguagePriority Prefer Fallback

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the 
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

#
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#
#AddType application/x-tar .tgz

#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz

# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
#   MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

#
# For files that include their own HTTP headers:
#
#AddHandler send-as-is asis

#
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
#  to be distributed in multiple languages.)
#
AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections.  We use 
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
#   Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /var/www/error/include/ files and
# copying them to /your/include/path/, even on a per-VirtualHost basis.
#

Alias /error/ "/var/www/error/"

 <ifmodule mod_negotiation.c=""><ifmodule mod_include.c=""><directory "="" var="" www="" error"="">AllowOverride None
        Options IncludesNoExec
        AddOutputFilter Includes html
        AddHandler type-map var
        Order allow,deny
        Allow from all
        LanguagePriority en es de fr
        ForceLanguagePriority Prefer Fallback</directory> 

#    ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
#    ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
#    ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
#    ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
#    ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
#    ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
#    ErrorDocument 410 /error/HTTP_GONE.html.var
#    ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
#    ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
#    ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
#    ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
#    ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
#    ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
#    ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
#    ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
#    ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
#    ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var</ifmodule></ifmodule> 

#
# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
#
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

#
# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash.  This fixes a 
# problem with Microsoft WebFolders which does not appropriately handle 
# redirects for folders with DAV methods.
# Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
#
BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
BrowserMatch "MS FrontPage" redirect-carefully
BrowserMatch "^WebDrive" redirect-carefully
BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully
BrowserMatch "^gnome-vfs/1.0" redirect-carefully
BrowserMatch "^XML Spy" redirect-carefully
BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully

#
# Allow server status reports generated by mod_status,
# with the URL of http://servername/server-status
# Change the ".example.com" to match your domain to enable.
#
# <location server-status="">#    SetHandler server-status
#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</location>

#
# Allow remote server configuration reports, with the URL of
#  http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".example.com" to match your domain to enable.
#
# <location server-info="">#    SetHandler server-info
#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</location>

#
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
# <ifmodule mod_proxy.c="">#ProxyRequests On
#
# <proxy *="">#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</proxy>

#
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#
#ProxyVia On

#
# To enable a cache of proxied content, uncomment the following lines.
# See http://httpd.apache.org/docs/2.2/mod/mod_cache.html for more details.
#
# <ifmodule mod_disk_cache.c="">#   CacheEnable disk /
#   CacheRoot "/var/cache/mod_proxy"
#</ifmodule>
#

#</ifmodule>
# End of proxy directives.

### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at 
# <url:http: httpd.apache.org="" docs="" 2.2="" vhosts=""># for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
  NameVirtualHost *:80
#
# NOTE: NameVirtualHost cannot be used without a port specifier 
# (e.g. :80) if mod_ssl is being used, due to the nature of the
# SSL protocol.
#

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
# <virtualhost *:80="">#    ServerAdmin webmaster@dummy-host.example.com
#    DocumentRoot /www/docs/dummy-host.example.com
#    ServerName dummy-host.example.com
#    ErrorLog logs/dummy-host.example.com-error_log
#    CustomLog logs/dummy-host.example.com-access_log common
#</virtualhost>

 <virtualhost *:80="">ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html/
    ServerName localhost
     ServerAlias http://localhost/
     <directory var="" www="" html="">AllowOverride all</directory> 
    ErrorLog logs/localhost-error_log
    CustomLog logs/localhost-access_log common</virtualhost> 

# <virtualhost *:80=""><virtualhost 12.34.56.78:443="">ServerAdmin webmaster@mydomain.com
    DocumentRoot /var/www/vhosts/mydomain.com/httpdocs/
    ServerName mydomain.com
     ServerAlias www.mydomain.com
     <directory var="" www="" vhosts="" mydomain.com="" httpdocs="">AllowOverride all</directory> 
    Alias /webmail  "/var/www/html/webmail/"
    Alias /postfixadmin  "/var/www/html/postfixadmin"
    ErrorLog logs/mydomain.com-error_log
    CustomLog logs/mydomain.com-access_log common
    SSLEngine on
    SSLCertificateFile /etc/httpd/ssl/www.mydomain.com.crt
    SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com-noencryption.key
    #SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com.key
    SSLCertificateChainFile /etc/httpd/ssl/mydomain_com.ca-bundle
    #SSLCACertificateFile /etc/httpd/ssl/mydomain_com.ca-bundle
    LogLevel warn</virtualhost> 

 <virtualhost *:80="">ServerAdmin webmaster@mydomain3.org
    DocumentRoot /var/www/vhosts/mydomain3.org/httpdocs/
    ServerName mydomain3.org
     ServerAlias www.mydomain3.org
     <directory var="" www="" vhosts="" mydomain3.org="" httpdocs="">AllowOverride all</directory> 
    Alias /webmail  "/var/www/html/webmail/"
    Alias /postfixadmin  "/var/www/html/postfixadmin"
    ErrorLog logs/mydomain3.org.com-error_log
    CustomLog logs/mydomain3.org-access_log common</virtualhost> 

 <virtualhost *:80="">ServerAdmin webmaster@mydomain4.com
    DocumentRoot /var/www/vhosts/mydomain4.com/httpdocs/
    ServerName mydomain4.com
     ServerAlias www.mydomain4.com
     <directory var="" www="" vhosts="" mydomain4.com="" httpdocs="">AllowOverride all</directory> 
    Alias /webmail  "/var/www/html/webmail/"
    Alias /postfixadmin  "/var/www/html/postfixadmin"
    ErrorLog logs/mydomain4.com-error_log
    CustomLog logs/mydomain4.com-access_log common</virtualhost></virtualhost></url:http:></error></error></virtualhost></virtualhost></virtualhost></virtualhost></virtualhost></virtualhost></virtualhost></virtualhost></url:http:></url:http:></url:http:> 

also, I should also add that I changed the owner of the files to Apache by doing: chown -R apache .

According to a thing I found on google: http://www.howtoforge.com/forums/showthread.php?t=46068

Which says something is wrong with the key. You created that key (the private key) with openssl right? Nothing manually copy/pasted in that key? Otherwise maybe something went wrong with the copy-paste of the private key.

If that's not the case, I'm not quite sure. The problem you have now is separate of Apache. You have a problem with your private key even before Apache tries to use it.

A side note: You're not required to have a passphrase for the private key. It adds some security, but if you have trouble remembering passwords it might be better to not use it or save it somewhere so that you don't lose it. Everytime Apache has to be restarted it will ask for the private key. If you don't use a passphrase you'll be able to restart without having to insert the password every time.

Hi @Nuvini,

Thanks a million for all the help.

I followed the instructions on the Linode library on installing SSL (http://library.linode.com/security/ssl- … commercial">http://library.linode.com/security/ssl-certificates/commercial) and I reinstalled the SSL certificate.

This time, I didn't use a pass phrase.

When it was time to start Apache, Apache started.

I pointed my browser to https://mydomain.com and got a warning:

This Connection is Untrusted

You have asked Firefox to connect securely to www.mydomain.com, but we can't confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified.

What Should I Do?
If you usually connect to
this site without problems, this error could mean that someone is
trying to impersonate the site, and you shouldn't continue.

       Technical Details
www.mydomain.com uses an invalid security certificate.

The certificate is only valid for mydomain.com

(Error code: ssl_error_bad_cert_domain)

          I Understand the Risks

Comparing the Virtual host block in the httpd.conf file and to server folder contents (for SSL)I realized that I didn't get this file in this new SSL installation process: mydomain_com.ca-bundle. Which is the same file the SSLCertificateChainFile points to.

Could this be the cause of the problem (the warnings)?

Otherwise, what have I done wrong this time?

How do I obtain the .ca-bundle file?

what is its use?

What could be the cause of this issue/problem?

Here is what the virtual host block in my httpd.conf now looks like (I commented out the unnecessary lines):

 <virtualhost 12.34.56.78:443="">ServerAdmin webmaster@mydomain.com
    DocumentRoot /var/www/vhosts/mydomain.com/httpdocs/
    ServerName mydomain.com
     ServerAlias www.mydomain.com
     <directory var="" www="" vhosts="" mydomain.com="" httpdocs="">AllowOverride all</directory> 
    Alias /webmail  "/var/www/html/webmail/"
    Alias /postfixadmin  "/var/www/html/postfixadmin"
    ErrorLog logs/mydomain.com-error_log
    CustomLog logs/mydomain.com-access_log common
    SSLEngine on
    SSLCertificateFile /etc/httpd/ssl/www.mydomain.com.crt
    #SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com-noencryption.key
    SSLCertificateKeyFile /etc/httpd/ssl/www.mydomain.com.key
    #SSLCertificateChainFile /etc/httpd/ssl/mydomain_com.ca-bundle
    #SSLCACertificateFile /etc/httpd/ssl/mydomain_com.ca-bundle
    LogLevel warn</virtualhost> 

What could be the cause of this issue/problem?

Thanks

I also just noticed that www.mydomain.com or mydomain.com brings up the Apache default page for CentOS.

I would have to do https://mydomain.com (and get past the warnings) to access the site.

Is this how it is supposed to work?

Are you sure there are no hidden redirects to https://www.mydomain.com? SSL Certificates are only for one domain, so either mydomain.com -or- http://www.mydomain.com. Not both.

Another note, though I'm no expert but I believe you make a CSR with your private key, and then request a signed certificate from Thawte. If you now change your private key without requesting a new SSL certificate you'll probably have to make a new CSR (with your new private key) and get it signed by Thawte in order for it to work. Though, the problem you're currently having is unrelated to that.

I believe it is the purpose of CA-bundles to contain the root and intermediate certificates from Thawte, since you're essentially creating kind of a "chain": your certificate all the way to Thawte's root certificate that has to be trusted.

On another note, is having the domain out here such a disaster? Now that you have Apache running it'd probably help with troubleshooting to be able to actually see your site and the certificate . Though not required, it might be faster :)

EDIT: As for the vhosts: It's separated, so you need to set up a vhost at :80 as well, but that one without SSL. If you want a https-only website you can set up the non-ssl vhost to rewrite/redirect to https.

Thanks Nuvini for the explanation.

I have sent the actual URL to your inbox here on the forum.

Didn't know I would have to create another virtual host block for the non-ssl access to the site. Thanks for that. Would do that now.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct