Google云实例上的WordPress SSLconfiguration

我正在尝试configuration托pipe在Google云上的Wordpress实例来使用https而不是http

我正按照这些说明设置它：

https://jamescoote.co.uk/add-letsencrypt-ssl-certificate-to-wordpress/

使用letsencrypt

• nginx https无法通过ie连接
• Kubernetes节点度量标准端点返回401
• 无法通过HTTP或HTTPS连接到Google Cloud服务器
• 重新configurationApache以通过HTTPS（而不是HTTP）提供Subversion存储库
• https到https在https中redirect的问题

我已经按照这些说明添加了证书。 我还将ssl.conf和ssl.load sylinked到启用mod。

我将certpath添加到default-ssl.conf，并将其链接到启用站点的地方，但是每当我这样做，我都无法重新启动Apache。 我得到这个消息：

apache2.service的apache2.serviceJob失败。 有关详细信息，请参阅“systemctl status apa che2.service”和“journalctl -xn”。

但是当我尝试这些命令时，并没有给我足够的信息来解决问题。

默认-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, eg #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, ie 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, ie 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：syntax = apache ts = 4 sw = 4 sts = 4 sr noet

当我检查证书是否被成功授予他们时。 我想有一些Apache的configuration，我没有申请的地方，但我不知道它是什么，任何指针将不胜感激。

谢谢

更多细节请求：

这是来自apache的错误日志的内容：

[Thu Feb 23 06：46：55.153392 2017] [mpm_prefork：notice] [pid 1215] AH00163：configurationApache / 2.4.10（Debian） – 恢复正常运行[Thu Feb 23 06：46：55.153424 2017] AH00094：命令行：'/ usr / sbin / apache2'[Thu Feb 23 06:51:40.656914 2017] [authz_core：error] [pid 12411] [client 146.148.7.38:50713] AH01630：client被服务器configuration拒绝：/var/www/html/wp-config.old，referer：hostname / wp-config.old [Thu Feb 23 07：42：52.938926 2017] [authz_core：error] [pid 12408] [client 146.148 .7.38：51000] AH01630：客户端拒绝服务器configuration：/var/www/html/wp-config.old，referer：hostname / wp-config.old [Thu Feb 23 11：09：56.509913 2017] [mpm_prefork：notice AH00169：发现SIGTERM，closures[Thu Feb 23 11：13：34.728029 2017] [mpm_prefork：notice] [pid 17535] AH00163：Apache / 2.4.10（Debian）configuration – 恢复正常运行[Thu 2月23日11：13：34.728083 2017] [核心：通知] [pid 17535] AH00094：命令行：'/ usr / sbin / apache2'

这不会引起我与这个问题有关，但也许我应该删除该文件（虽然从虚拟主机文件中删除443节开始，

这是来自systemctl的消息：

无法获得D-Bus连接：没有这样的文件或目录 – 我已经将virtualHost部分添加到我的wordpress.conf中以便在443上进行收听，这是我在开始时尝试的。

 <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>