A few issues, NXdomain error, SSLcert file empty, failed auth procedure


#21

Please show:
sudo netstat -pant | grep -E '80|443'


#22

tcp6 0 0 :::80 :::* LISTEN 1332/apache2


#23

It seems to NOT be listening on port 443


#24

Please show the vhost file for rafflegiftcards.com
If you are not sure where the vhost file is… (neither am I).
Try finding it with:
sudo grep -Eri 'known|challenge|VirtualHost|ServerName|ServerAlias|SSLCertificateFile' /opt/bitnami/apache2


#25

seems to be all the vhost have dummy info, im going to change them real quick.


#26

Virtual Hosts

Required modules: mod_log_config

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.4/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.

VirtualHost example:

Almost any Apache directive may go into a VirtualHost container.

The first VirtualHost section is used for all requests that do not

match a ServerName or ServerAlias in any block.

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
ServerName dummy-host.example.com
ServerAlias www.dummy-host.example.com
ErrorLog “logs/dummy-host.example.com-error_log”
CustomLog “logs/dummy-host.example.com-access_log” common

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
ServerName dummy-host2.example.com
ErrorLog “logs/dummy-host2.example.com-error_log”
CustomLog “logs/dummy-host2.example.com-access_log” common


#27

this prob a better view

/opt/bitnami/apache2/conf/extra/httpd-default.conf:# ServerName directive.
/opt/bitnami/apache2/conf/extra/httpd-multilang-errordoc.conf:# even on a per-VirtualHost basis. The default include files will display
/opt/bitnami/apache2/conf/extra/httpd-info.conf:# with the URL of http://servername/server-status
/opt/bitnami/apache2/conf/extra/httpd-info.conf:# http://servername/server-info (requires that mod_info.c be loaded).
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# machine you can setup VirtualHost containers for them. Most configurations
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# VirtualHost example:
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# Almost any Apache directive may go into a VirtualHost container.
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# The first VirtualHost section is used for all requests that do not
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# match a ServerName or ServerAlias in any block.
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:<VirtualHost *:80>
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: ServerName dummy-host.example.com
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: ServerAlias www.dummy-host.example.com
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:<VirtualHost *:80>
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: ServerName dummy-host2.example.com
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:ServerName www.example.com:443
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:# Point SSLCertificateFile at a PEM encoded certificate. If
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:SSLCertificateFile “/opt/bitnami/apache2/conf/server.crt”
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:#SSLCertificateFile “/opt/bitnami/apache2/conf/server-dsa.crt”
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:#SSLCertificateFile “/opt/bitnami/apache2/conf/server-ecc.crt”
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:# the referenced file can be the same as SSLCertificateFile
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:
/opt/bitnami/apache2/conf/bitnami/bitnami.conf: NameVirtualHost :80
/opt/bitnami/apache2/conf/bitnami/bitnami.conf: NameVirtualHost :443
/opt/bitnami/apache2/conf/bitnami/bitnami.conf:
/opt/bitnami/apache2/conf/bitnami/bitnami.conf:
/opt/bitnami/apache2/conf/bitnami/bitnami.conf:
/opt/bitnami/apache2/conf/bitnami/bitnami.conf:SSLCertificateFile “/opt/bitnami/apache2/conf/server.crt”
/opt/bitnami/apache2/conf/bitnami/bitnami.conf:
/opt/bitnami/apache2/conf/httpd.conf:# ports, instead of the default. See also the
/opt/bitnami/apache2/conf/httpd.conf:# definition. These values also provide defaults for
/opt/bitnami/apache2/conf/httpd.conf:# any containers you may define later in the file.
/opt/bitnami/apache2/conf/httpd.conf:# All of these directives may appear inside containers,
/opt/bitnami/apache2/conf/httpd.conf:# ServerName gives the name and port that the server uses to identify itself.
/opt/bitnami/apache2/conf/httpd.conf:ServerName localhost:80
/opt/bitnami/apache2/conf/httpd.conf:# If you do not specify an ErrorLog directive within a
/opt/bitnami/apache2/conf/httpd.conf:# logged here. If you do define an error logfile for a
/opt/bitnami/apache2/conf/httpd.conf: # If you do not define any access logfiles within a
/opt/bitnami/apache2/conf/httpd.conf: # define per- access logfiles, transactions will be
/opt/bitnami/apache2/conf/original/extra/httpd-default.conf:# ServerName directive.
/opt/bitnami/apache2/conf/original/extra/httpd-multilang-errordoc.conf:# even on a per-VirtualHost basis. The default include files will display
/opt/bitnami/apache2/conf/original/extra/httpd-info.conf:# with the URL of http://servername/server-status
/opt/bitnami/apache2/conf/original/extra/httpd-info.conf:# http://servername/server-info (requires that mod_info.c be loaded).
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# machine you can setup VirtualHost containers for them. Most configurations
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# VirtualHost example:
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# Almost any Apache directive may go into a VirtualHost container.
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# The first VirtualHost section is used for all requests that do not
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# match a ServerName or ServerAlias in any block.
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:<VirtualHost :80>
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: ServerName dummy-host.example.com
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: ServerAlias www.dummy-host.example.com
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:<VirtualHost :80>
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: ServerName dummy-host2.example.com
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:ServerName www.example.com:443
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:# Point SSLCertificateFile at a PEM encoded certificate. If
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:SSLCertificateFile “/opt/bitnami/apache2/conf/server.crt”
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:#SSLCertificateFile “/opt/bitnami/apache2/conf/server-dsa.crt”
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:#SSLCertificateFile “/opt/bitnami/apache2/conf/server-ecc.crt”
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:# the referenced file can be the same as SSLCertificateFile
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:
/opt/bitnami/apache2/conf/original/httpd.conf:# ports, instead of the default. See also the
/opt/bitnami/apache2/conf/original/httpd.conf:# definition. These values also provide defaults for
/opt/bitnami/apache2/conf/original/httpd.conf:# any containers you may define later in the file.
/opt/bitnami/apache2/conf/original/httpd.conf:# All of these directives may appear inside containers,
/opt/bitnami/apache2/conf/original/httpd.conf:# ServerName gives the name and port that the server uses to identify itself.
/opt/bitnami/apache2/conf/original/httpd.conf:#ServerName www.example.com:80
/opt/bitnami/apache2/conf/original/httpd.conf:# If you do not specify an ErrorLog directive within a
/opt/bitnami/apache2/conf/original/httpd.conf:# logged here. If you do define an error logfile for a
/opt/bitnami/apache2/conf/original/httpd.conf: # If you do not define any access logfiles within a
/opt/bitnami/apache2/conf/original/httpd.conf: # define per- access logfiles, transactions will be
Binary file /opt/bitnami/apache2/modules/mod_pagespeed.so matches
Binary file /opt/bitnami/apache2/modules/mod_ssl.so matches
Binary file /opt/bitnami/apache2/modules/libphp7.so matches
Binary file /opt/bitnami/apache2/modules/mod_pagespeed_ap24.so matches
Binary file /opt/bitnami/apache2/modules/mod_log_config.so matches
Binary file /opt/bitnami/apache2/modules/mod_security2.so matches
/opt/bitnami/apache2/include/httpd.h: * The address 255.255.255.255, when used as a virtualhost address,
/opt/bitnami/apache2/include/httpd.h: /
The name given in “” /
/opt/bitnami/apache2/include/httpd.h: /
Normal names for ServerAlias servers /
/opt/bitnami/apache2/include/httpd.h: /
Wildcarded names for ServerAlias servers /
/opt/bitnami/apache2/include/http_config.h:#define NOT_IN_VIRTUALHOST 0x01 /*< Forbidden in <VirtualHost> /
/opt/bitnami/apache2/include/http_config.h:/
Forbidden in <VirtualHost>/<Limit>/<Directory>/<Location>/<Files>/<If><Proxy>
/
/opt/bitnami/apache2/include/http_config.h:#define GLOBAL_ONLY (NOT_IN_VIRTUALHOST|NOT_IN_DIR_CONTEXT)
/opt/bitnami/apache2/include/http_vhost.h: * handle addresses in “” statement
/opt/bitnami/apache2/include/http_vhost.h: * @param hostname The hostname in the VirtualHost statement
/opt/bitnami/apache2/include/http_vhost.h: * handle NameVirtualHost directive
Binary file /opt/bitnami/apache2/bin/httpd.bin matches


#28

Agreed; all those files are unused or unrelated.

There should be one with “rafflegiftcards.com” in it…
But since I don’t know where Bitnami places its’ vhost config files, I am unable to locate it.


#29

I’ve found the 2 vhost file that Bitnami uses per there doc. one has this output:

App url moved to root

DocumentRoot “/opt/bitnami/apps/wordpress/htdocs”
#Alias /wordpress/ “/opt/bitnami/apps/wordpress/htdocs/”
#Alias /wordpress “/opt/bitnami/apps/wordpress/htdocs”

RewriteEngine On
RewriteCond “%{HTTP_HOST}” ^ec2-([0-9]{1,3})-([0-9]{1,3})-([0-9]{1,3})-([0-9]{1,3})….amazonaws.com(:[0-9])?$
RewriteRule “^/?(.*)” “%{REQUEST_SCHEME}://%1.%2.%3.%4%5/$1” [L,R=302,NE]

Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf

2nd output:

VirtualHost *:80>
ServerName wordpress.example.com
ServerAlias www.wordpress.example.com
DocumentRoot “/opt/bitnami/apps/wordpress/htdocs”

Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"

<VirtualHost *:443>
ServerName wordpress.example.com
ServerAlias www.wordpress.example.com
DocumentRoot “/opt/bitnami/apps/wordpress/htdocs”
SSLEngine on
SSLCertificateFile “/opt/bitnami/apps/wordpress/conf/certs/server.crt”
SSLCertificateKeyFile “/opt/bitnami/apps/wordpress/conf/certs/server.key”

Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
~ ~

#30

The second one looks like it would do the job.
You just need to update the details to match the site and cert.
The cert is at:


#31

I’ve changed it to look like the below, but apache2 still will not run nor can I run the cert again for the www mydomain

<VirtualHost *:80>
    ServerName rafflegiftcards.com
    ServerAlias www.rafflegiftcards.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"

    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>

<VirtualHost *:443>
    ServerName rafflegiftcards.com
    ServerAlias www.rafflegiftcards.com
    DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"
    SSLEngine on
    SSLCertificateFile "/etc/letsencrypt/live/rafflegiftcards.com/fullchain.pem"
    SSLCertificateKeyFile "/etc/letsencrypt/live/rafflegiftcards.com/privkey.pem"

    Include "/opt/bitnami/apps/wordpress/conf/httpd-app.conf"
</VirtualHost>
~

#32

Show output of:
apachectl configtest


#33

it did no put anything but syntax OK


#34

Please show:
sudo grep -Eri 'DocumentRoot|Servername' /opt/bitnami/apache2


#35

/opt/bitnami/apache2/conf/extra/httpd-default.conf:# ServerName directive.
/opt/bitnami/apache2/conf/extra/httpd-info.conf:# with the URL of http://servername/server-status
/opt/bitnami/apache2/conf/extra/httpd-info.conf:# http://servername/server-info (requires that mod_info.c be loaded).
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf:# match a ServerName or ServerAlias in any block.
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: ServerName rafflegiftcards.com
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf: ServerName rafflegiftcards.com
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/extra/httpd-ssl.conf:ServerName www.example.com:443
/opt/bitnami/apache2/conf/bitnami/bitnami.conf: DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/bitnami/bitnami.conf: DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/httpd.conf:# ServerName gives the name and port that the server uses to identify itself.
/opt/bitnami/apache2/conf/httpd.conf:ServerName localhost:80
/opt/bitnami/apache2/conf/httpd.conf:# DocumentRoot: The directory out of which you will serve your
/opt/bitnami/apache2/conf/httpd.conf:DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/httpd.conf: # access content that does not live under the DocumentRoot.
/opt/bitnami/apache2/conf/original/extra/httpd-default.conf:# ServerName directive.
/opt/bitnami/apache2/conf/original/extra/httpd-info.conf:# with the URL of http://servername/server-status
/opt/bitnami/apache2/conf/original/extra/httpd-info.conf:# http://servername/server-info (requires that mod_info.c be loaded).
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf:# match a ServerName or ServerAlias in any block.
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: ServerName rafflegiftcards.com
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
/opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf: ServerName rafflegiftcards.com
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf:ServerName www.rafflegiftcards.com:443
/opt/bitnami/apache2/conf/original/httpd.conf:# ServerName gives the name and port that the server uses to identify itself.
/opt/bitnami/apache2/conf/original/httpd.conf:#ServerName www.example.com:80
/opt/bitnami/apache2/conf/original/httpd.conf:# DocumentRoot: The directory out of which you will serve your
/opt/bitnami/apache2/conf/original/httpd.conf:DocumentRoot “/opt/bitnami/apache2/htdocs”
/opt/bitnami/apache2/conf/original/httpd.conf: # access content that does not live under the DocumentRoot.
Binary file /opt/bitnami/apache2/modules/mod_pagespeed.so matches
Binary file /opt/bitnami/apache2/modules/mod_ssl.so matches
Binary file /opt/bitnami/apache2/modules/libphp7.so matches
Binary file /opt/bitnami/apache2/modules/mod_pagespeed_ap24.so matches
Binary file /opt/bitnami/apache2/modules/mod_vhost_alias.so matches
/opt/bitnami/apache2/include/httpd.h: * Default location of documents. Can be overridden by the DocumentRoot
Binary file /opt/bitnami/apache2/bin/httpd.bin matches


#36

Please show (individual posts):
sudo more /opt/bitnami/apache2/conf/extra/httpd-vhosts.conf
sudo more /opt/bitnami/apache2/conf/original/extra/httpd-vhosts.conf
sudo more /opt/bitnami/apache2/conf/original/extra/httpd-ssl.conf


#37

Virtual Hosts

Required modules: mod_log_config

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.4/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.

VirtualHost example:

Almost any Apache directive may go into a VirtualHost container.

The first VirtualHost section is used for all requests that do not

match a ServerName or ServerAlias in any block.

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
ServerName rafflegiftcards.com
ServerAlias www.dummy-host.example.com
ErrorLog “logs/dummy-host.example.com-error_log”
CustomLog “logs/dummy-host.example.com-access_log” common

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
ServerName rafflegiftcards.com
ErrorLog “logs/dummy-host2.example.com-error_log”
CustomLog “logs/dummy-host2.example.com-access_log” common


#38

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
ServerName rafflegiftcards.com
ServerAlias www.rafflegiftcards.com
ErrorLog “logs/dummy-host.example.com-error_log”
CustomLog “logs/dummy-host.example.com-access_log” common

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
ServerName rafflegiftcards.com
ErrorLog “logs/dummy-host2.example.com-error_log”
CustomLog “logs/dummy-host2.example.com-access_log” common


#39

This is the Apache server configuration file providing SSL support.

It contains the configuration directives to instruct the server how to

serve pages over an https connection. For detailed information about these

directives see URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html

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.

Required modules: mod_log_config, mod_setenvif, mod_ssl,

socache_shmcb_module (for default value of SSLSessionCache)

Pseudo Random Number Generator (PRNG):

Configure one or more sources to seed the PRNG of the SSL library.

The seed data should be of good random quality.

WARNING! On some platforms /dev/random blocks if not enough entropy

is available. This means you then cannot use the /dev/random device

because it would lead to very long connection times (as long as

it requires to make more entropy available). But usually those

platforms additionally provide a /dev/urandom device which doesn’t

block. So, if available, use this one instead. Read the mod_ssl User

Manual for more details.

#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

When we also provide SSL we have to listen to the

standard HTTP port (see above) and to the HTTPS port

Listen 443

SSL Global Context

All SSL configuration in this context applies both to

the main server and all SSL-enabled virtual hosts.

SSL Cipher Suite:

List the ciphers that the client is permitted to negotiate,

and that httpd will negotiate as the client of a proxied server.

See the OpenSSL documentation for a complete list of ciphers, and

ensure these follow appropriate best practices for this deployment.

httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers,

while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a.

SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES

By the end of 2016, only TLSv1.2 ciphers should remain in use.

Older ciphers should be disallowed as soon as possible, while the

kRSA ciphers do not offer forward secrecy. These changes inhibit

older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy

non-browser tooling) from successfully connecting.

To restrict mod_ssl to use only TLSv1.2 ciphers, and disable

those protocols which do not support forward secrecy, replace

the SSLCipherSuite and SSLProxyCipherSuite directives above with

the following two directives, as soon as practical.

SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA

SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA

User agents such as web browsers are not configured for the user’s

own preference of either security or performance, therefore this

must be the prerogative of the web server administrator who manages

cpu load versus confidentiality, so enforce the server’s cipher order.

SSLHonorCipherOrder on

SSL Protocol support:

List the protocol versions which clients are allowed to connect with.

Disable SSLv3 by default (cf. RFC 7525 3.1.1). TLSv1 (1.0) should be

disabled as quickly as practical. By the end of 2016, only the TLSv1.2

protocol or later should remain in use.

SSLProtocol all -SSLv3
SSLProxyProtocol all -SSLv3

Pass Phrase Dialog:

Configure the pass phrase gathering process.

The filtering dialog program (`builtin’ is an internal

terminal dialog) has to provide the pass phrase on stdout.

SSLPassPhraseDialog builtin

Inter-Process Session Cache:

Configure the SSL Session Cache: First the mechanism

to use and second the expiring timeout (in seconds).

#SSLSessionCache “dbm:/opt/bitnami/apache2/logs/ssl_scache”
SSLSessionCache “shmcb:/opt/bitnami/apache2/logs/ssl_scache(512000)”
SSLSessionCacheTimeout 300

OCSP Stapling (requires OpenSSL 0.9.8h or later)

This feature is disabled by default and requires at least

the two directives SSLUseStapling and SSLStaplingCache.

Refer to the documentation on OCSP Stapling in the SSL/TLS

How-To for more information.

Enable stapling for all SSL-enabled servers:

#SSLUseStapling On

Define a relatively small cache for OCSP Stapling using

the same mechanism that is used for the SSL session cache

above. If stapling is used with more than a few certificates,

the size may need to be increased. (AH01929 will be logged.)

#SSLStaplingCache “shmcb:/opt/bitnami/apache2/logs/ssl_stapling(32768)”

Seconds before valid OCSP responses are expired from the cache

#SSLStaplingStandardCacheTimeout 3600

Seconds before invalid OCSP responses are expired from the cache

#SSLStaplingErrorCacheTimeout 600

SSL Virtual Host Context

General setup for the virtual host

DocumentRoot “/opt/bitnami/apache2/htdocs”
ServerName www.rafflegiftcards.com:443
ServerAdmin you@example.com
ErrorLog “/opt/bitnami/apache2/logs/error_log”
TransferLog “/opt/bitnami/apache2/logs/access_log”

SSL Engine Switch:

Enable/Disable SSL for this virtual host.

SSLEngine on

Server Certificate:

Point SSLCertificateFile at a PEM encoded certificate. If

the certificate is encrypted, then you will be prompted for a

pass phrase. Note that a kill -HUP will prompt again. Keep

in mind that if you have both an RSA and a DSA certificate you

can configure both in parallel (to also allow the use of DSA

ciphers, etc.)

Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)

require an ECC certificate which can also be configured in

parallel.

SSLCertificateFile “/opt/bitnami/apache2/conf/server.crt”
#SSLCertificateFile “/opt/bitnami/apache2/conf/server-dsa.crt”
#SSLCertificateFile “/opt/bitnami/apache2/conf/server-ecc.crt”

Server Private Key:

If the key is not combined with the certificate, use this

directive to point at the key file. Keep in mind that if

you’ve both a RSA and a DSA private key you can configure

both in parallel (to also allow the use of DSA ciphers, etc.)

ECC keys, when in use, can also be configured in parallel

SSLCertificateKeyFile “/opt/bitnami/apache2/conf/server.key”
#SSLCertificateKeyFile “/opt/bitnami/apache2/conf/server-dsa.key”
#SSLCertificateKeyFile “/opt/bitnami/apache2/conf/server-ecc.key”

Server Certificate Chain:

Point SSLCertificateChainFile at a file containing the

concatenation of PEM encoded CA certificates which form the

certificate chain for the server certificate. Alternatively

the referenced file can be the same as SSLCertificateFile

when the CA certificates are directly appended to the server

certificate for convenience.

#SSLCertificateChainFile “/opt/bitnami/apache2/conf/server-ca.crt”

Certificate Authority (CA):

Set the CA certificate verification path where to find CA

certificates for client authentication or alternatively one

huge file containing all of them (file must be PEM encoded)

Note: Inside SSLCACertificatePath you need hash symlinks

to point to the certificate files. Use the provided

Makefile to update the hash symlinks after changes.

#SSLCACertificatePath “/opt/bitnami/apache2/conf/ssl.crt”
#SSLCACertificateFile “/opt/bitnami/apache2/conf/ssl.crt/ca-bundle.crt”

Certificate Revocation Lists (CRL):

Set the CA revocation path where to find CA CRLs for client

authentication or alternatively one huge file containing all

of them (file must be PEM encoded).

The CRL checking mode needs to be configured explicitly

through SSLCARevocationCheck (defaults to “none” otherwise).

Note: Inside SSLCARevocationPath you need hash symlinks

to point to the certificate files. Use the provided

Makefile to update the hash symlinks after changes.

#SSLCARevocationPath “/opt/bitnami/apache2/conf/ssl.crl”
#SSLCARevocationFile “/opt/bitnami/apache2/conf/ssl.crl/ca-bundle.crl”
#SSLCARevocationCheck chain

Client Authentication (Type):

Client certificate verification type and depth. Types are

none, optional, require and optional_no_ca. Depth is a

number which specifies how deeply to verify the certificate

issuer chain before deciding the certificate is not valid.

#SSLVerifyClient require
#SSLVerifyDepth 10

TLS-SRP mutual authentication:

Enable TLS-SRP and set the path to the OpenSSL SRP verifier

file (containing login information for SRP user accounts).

Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for

detailed instructions on creating this file. Example:

“openssl srp -srpvfile /opt/bitnami/apache2/conf/passwd.srpv -add username”

#SSLSRPVerifierFile “/opt/bitnami/apache2/conf/passwd.srpv”

Access Control:

With SSLRequire you can do per-directory access control based

on arbitrary complex boolean expressions containing server

variable checks and other lookup directives. The syntax is a

mixture between C and Perl. See the mod_ssl documentation

for more details.

#
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \

and %{SSL_CLIENT_S_DN_O} eq “Snake Oil, Ltd.” \

and %{SSL_CLIENT_S_DN_OU} in {“Staff”, “CA”, “Dev”} \

and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \

and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \

or %{REMOTE_ADDR} =~ m/^192.76.162.[0-9]+$/

#

SSL Engine Options:

Set various options for the SSL engine.

o FakeBasicAuth:

Translate the client X.509 into a Basic Authorisation. This means that

the standard Auth/DBMAuth methods can be used for access control. The

user name is the `one line’ version of the client’s X.509 certificate.

Note that no password is obtained from the user. Every entry in the user

file needs this password: `xxj31ZMTZzkVA’.

o ExportCertData:

This exports two additional environment variables: SSL_CLIENT_CERT and

SSL_SERVER_CERT. These contain the PEM-encoded certificates of the

server (always existing) and the client (only existing when client

authentication is used). This can be used to import the certificates

into CGI scripts.

o StdEnvVars:

This exports the standard SSL/TLS related `SSL_*’ environment variables.

Per default this exportation is switched off for performance reasons,

because the extraction step is an expensive operation and is usually

useless for serving static content. So one usually enables the

exportation for CGI and SSI requests only.

o StrictRequire:

This denies access when “SSLRequireSSL” or “SSLRequire” applied even

under a “Satisfy any” situation, i.e. when it applies access is denied

and no other module can change it.

o OptRenegotiate:

This enables optimized SSL connection renegotiation handling when SSL

directives are used in per-directory context.

#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch “.(cgi|shtml|phtml|php)$”>
SSLOptions +StdEnvVars

<Directory “/opt/bitnami/apache2/cgi-bin”>
SSLOptions +StdEnvVars

SSL Protocol Adjustments:

The safe and default but still SSL/TLS standard compliant shutdown

approach is that mod_ssl sends the close notify alert but doesn’t wait for

the close notify alert from client. When you need a different shutdown

approach you can use one of the following variables:

o ssl-unclean-shutdown:

This forces an unclean shutdown when the connection is closed, i.e. no

SSL close notify alert is sent or allowed to be received. This violates

the SSL/TLS standard but is needed for some brain-dead browsers. Use

this when you receive I/O errors because of the standard approach where

mod_ssl sends the close notify alert.

o ssl-accurate-shutdown:

This forces an accurate shutdown when the connection is closed, i.e. a

SSL close notify alert is send and mod_ssl waits for the close notify

alert of the client. This is 100% SSL/TLS standard compliant, but in

practice often causes hanging connections with brain-dead browsers. Use

this only for browsers where you know that their SSL implementation

works correctly.

Notice: Most problems of broken clients are also related to the HTTP

keep-alive facility, so you usually additionally want to disable

keep-alive for those clients, too. Use variable “nokeepalive” for this.

Similarly, one has to force some clients to use HTTP/1.0 to workaround

their broken HTTP/1.1 implementation. Use variables “downgrade-1.0” and

“force-response-1.0” for this.

BrowserMatch “MSIE [2-5]”
nokeepalive ssl-unclean-shutdown
downgrade-1.0 force-response-1.0

Per-Server Logging:

The home of a custom SSL log file. Use this when you want a

compact non-error SSL logfile on a virtual host basis.

CustomLog “/opt/bitnami/apache2/logs/ssl_request_log”
“%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x “%r” %b”


#40

Update file:
/opt/bitnami/apache2/conf/extra/httpd-vhosts.conf
Remove the virtualhost sections:

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host.example.com”
ServerName rafflegiftcards.com
ServerAlias www.dummy-host.example.com
ErrorLog “logs/dummy-host.example.com-error_log”
CustomLog “logs/dummy-host.example.com-access_log” common

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.example.com
DocumentRoot “/opt/bitnami/apache2/docs/dummy-host2.example.com”
ServerName rafflegiftcards.com
ErrorLog “logs/dummy-host2.example.com-error_log”
CustomLog “logs/dummy-host2.example.com-access_log” common