我正在尝试配置托管在 Google 云上的 Wordpress 实例以使用 https 而不是 http
我正在尝试按照以下说明进行设置：
https://jamescoote.co.uk/add-letsencrypt-ssl-certificate-to-wordpress/
使用 letsencrypt
我已按照这些说明添加并安装了证书。我还将 ssl.conf 和 ssl.load 链接到 mod-enabled 中。
我将证书路径添加到 default-ssl.conf 中，并将其符号链接到 sites-enabled 中，但每当我这样做时，我都无法重新启动 apache。我收到以下消息：
apache2.service 的 apache2.serviceJob 失败。请参阅“systemctl status apa che2.service”和“journalctl -xn”了解详情。
但是当我尝试这些命令时，它并没有给我足够的信息来解决问题。
default-ssl.conf 的内容如下所示（我更改了主机名，但其余部分保持原样）：
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
# 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/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
SSLCertificate /etc/letsencrypt/live/hostname/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/hostname/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/hostname/fullchain.pem
# 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
# 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 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>
# vim: 语法=apache ts=4 sw=4 sts=4 sr noet
当我检查证书是否已成功授予时，他们说已经授予了。我猜有些 Apache 配置我还没有应用到某个地方，但我搞不清楚它是什么，任何指点都将不胜感激。
谢谢
根据要求提供更多详细信息：
这是来自 apache 的错误日志的内容：
[2017 年 2 月 23 日星期四 06：46：55.153392] [mpm_prefork：notice] [pid 1215] AH00163：Apache/2.4.10（Debian）已配置 - 恢复正常操作 [2017 年 2 月 23 日星期四 06：46：55.153424] [core：notice] [pid 1215] AH00094：命令行：'/usr/sbin/apache2' [2017 年 2 月 23 日星期四 06：51：40.656914] [authz_core：error] [pid 12411] [客户端 146.148.7.38:50713] AH01630：服务器配置拒绝客户端：/var/www/html/wp-config.old，引用者：hostname/wp-config.old [2017 年 2 月 23 日星期四 07：42：52.938926] [authz_core：error] [pid 12408] [client 146.148.7.38:51000] AH01630：服务器配置拒绝客户端：/var/www/html/wp-config.old，引用者：hostname/wp-config.old [2017 年 2 月 23 日星期四 11：09：56.509913] [mpm_prefork：notice] [pid 1215] AH00169：捕获 SIGTERM，正在关闭 [2017 年 2 月 23 日星期四 11：13：34.728029] [mpm_prefork：notice] [pid 17535] AH00163：Apache/2.4.10（Debian）已配置 - 恢复正常操作[2017 年 2 月 23 日星期四 11：13：34.728083] [core：notice] [pid 17535] AH00094：命令行：'/usr/sbin/apache2'
这并不让我感到与问题相关，但也许我应该删除该文件（虽然当我从虚拟主机文件中删除 443 部分时它可以正常启动）
这是来自 systemctl 的消息：
无法获取 D-Bus 连接：没有此文件或目录 - 我已将 virtualHost 部分添加到我的 wordpress.conf 以监听 443，这是我最初开始执行此操作时尝试过的。
答案1
原来问题是这样的：
SSL证书
本来应该
SSL证书文件
答案2
这些证书应该添加到您的 VirtualHost 文件中，而不是添加到您的 default-ssl.conf 文件中。
<VirtualHost *:443>
ServerName www.example.com
SSLEngine on
SSLCertificate /etc/letsencrypt/live/hostname/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/hostname/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/hostname/fullchain.pem
</VirtualHost>
发布上面提到的错误日志的结果也是很好的。