我在 Ubuntu Linux 上有一个 ZendServer。ZendServer 使用 Apache2，因此我正在寻找合适的配置来设置一组带有 SSL 的虚拟主机。
由于它是空白的，我不再使用它httpd.conf，并且我假设不再使用？
因此我一直在修改../sites-enabled/default和 ../sites-enabled/default-ssl
这是我所得到的（尽管服务器正常启动，但找不到 SSL 主机。
如果我删除对“ ”的引用IfModule mod_ssl.c，我会收到 SSL 错误，提示证书太长。
几个问题：
- 我在 NameVirtualHost 配置上做错了什么
- 如果我想为每个站点指定用于 SSL 的单独 IP 地址，则此配置不起作用 - 所以我在哪里引用这些 IP 地址？
- SSL 证书文件：我下载了.PEM来自 Parallels 的文件，因此它应该包含证书密钥，所以我将该引用更改为单个：
SSLCertificateFile
更新：我如何让它工作
由于我使用的是基本上未配置的 ZendServer 5.5 + Apache2 版本，我认为我对基本的 vhosts 设置感到非常困惑，感谢你们让我走上正确的轨道，使用 SH 命令来让事情正常运转。
由于我使用ZendServer 5.5.0 + Apache2我认为配置与大多数人习惯的配置略有不同，我按照说明进行操作这里很小心。
一旦我能够在正确的位置创建配置文件，我就能够使用命令：
$ a2ensite my_site_config_filename&$ a2dissite my_site_config_filename在重新启动 zend-server 之前启用和禁用站点。请记住，如果我对 上的各个站点的配置文件进行了更改
/apache2/sites-avaliable，我将使用前面提到的命令禁用并重新启用（似乎有必要让 apache2 重建符号链接或类似的东西……不确定这是否有必要但它是有意义的）
我也运行了
a2dissite default&，a2dissite default-ssl因为它们似乎与我新创建的配置相冲突。
- SSL：我将 SSL 的配置放在与端口 80 文件相同的配置文件中，如下所示（我使用自己的证书，但在此代码中我只指向来自 apache 的“snake-oil-cert”！）。
而且当然跑步：
$ a2enmod ssl（根据 cjc 的原始回答！）
/apache2/sites-avaliable/我的网站
#
# mysitename.com (/etc/apache2/sites-available/www.mysitename.com)
#
<VirtualHost *:80>
ServerAdmin [email protected]
ServerName mysitename.com
ServerAlias mysitename.com
# Indexes + Directory Root.
DocumentRoot /var/www/www.mysitename.com/htdocs/
# CGI Directory
ScriptAlias /cgi-bin/ /var/www/www.mysitename.com/cgi-bin/
<Location /cgi-bin>
Options +ExecCGI
</Location>
# Logfiles
ErrorLog /var/www/www.mysitename.com/logs/error.log
CustomLog /var/www/www.mysitename.com/logs/access.log combined
</VirtualHost>
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerAdmin webmaster@localhost
ServerName maryshop.com
ServerAlias maryshop.com
DocumentRoot /var/www/www.mysitename.com/htdocs/
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
<Directory "/usr/lib/cgi-bin">
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
Alias /doc/ "/usr/share/doc/"
<Directory "/usr/share/doc/">
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from 127.0.0.0/255.0.0.0 ::1/128
</Directory>
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# A self-signed (snakeoil) certificate can be created by installing
# the ssl-cert package. See
# /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
# If both key and certificate are stored in the same file, only the
# SSLCertificateFile directive is needed.
SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.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 convinience.
#SSLCertificateChainFile /etc/apache2/ssl.crt/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 /etc/ssl/certs/
#SSLCACertificateFile /etc/apache2/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)
# 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 /etc/apache2/ssl.crl/
#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
# 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
# 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.
#<Location />
#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]+$/
#</Location>
# 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
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
# 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 send or allowed to 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-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
</VirtualHost>
</IfModule>
/apache2/conf.d/virtual.conf
#
# We're running multiple virtual hosts.
#
NameVirtualHost *:80
/apache2/conf.d/virtual-ssl.conf
#
# We're running multiple virtual hosts.
#
NameVirtualHost *:443
答案1
您是否使用“a2enmod”启用了 SSL 模块？这类似于 sites-available/sites-enabled，其中从 mods-enabled 到 mods-available 中的文件创建符号链接。
要使用 IP 地址，请将其放在 VirtualHost 行中，例如<VirtualHost 192.168.1.1:443>.