Acontece que o problema era este:
SSLCertificate
deveria ter sido
SSLCertificateFile
Estou tentando configurar uma instância do Wordpress hospedada na nuvem do Google para usar https em vez de http
Estou tentando configurá-lo de acordo com estas instruções:
para usar o letsencrypt
Eu adicionei os certificados instalados de acordo com essas instruções. Eu também vinculei ssl.conf e ssl.load ao mod-enabled.
Eu adicionei os caminhos do certificado no default-ssl.conf e criei um link simbólico para sites habilitados, mas sempre que faço isso, não consigo fazer o apache reiniciar. Eu recebo esta mensagem:
apache2.serviceJob para apache2.service falhou. Veja 'statusctl status apa che2.service 'e' journalctl -xn 'para detalhes.
mas quando eu tento esses comandos não me dá informações suficientes para resolver o problema.
O conteúdo do default-ssl.conf se parece com isso (eu mudei o nome do host, mas o resto é como está):
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>
quando eu verifiquei se os certificados foram concedidos com sucesso. Eu acho que há algumas configurações do Apache que eu não apliquei em algum lugar, mas não consigo descobrir o que é, qualquer ponteiro seria apreciado.
Obrigado
Mais detalhes, conforme solicitado:
Este é o conteúdo do log de erros do apache:
[qui 23 de fevereiro 06: 46: 55.153392 2017] [mpm_prefork: notice] [pid 1215] AH00163: Apache / 2.4.10 (Debian) configurado - retomando as operações normais [Qui 23 de fevereiro 06: 46: 55.153424 2017] [core: aviso] [pid 1215] AH00094: Linha de comando: '/ usr / sbin / apache2' [Qui 23 de fevereiro 06: 51: 40.656914 2017] [authz_core: erro] [pid 12411] [cliente 146.148.7.38:50713] AH01630: cliente negado pela configuração do servidor: /var/www/html/wp-config.old, referer : hostname / wp-config.old [Qui 23 de fevereiro 07: 42: 52.938926 2017] [authz_core: error] [pid 12408] [cliente 146.148.7.38:51000] AH01630: cliente negado pela configuração do servidor: /var/www/html/wp-config.old, referer : hostname / wp-config.old [Qui 23 de fevereiro 11: 09: 56.509913 2017] [mpm_prefork: notice] [pid 1215] AH00169: pego SIGTERM, desligando [Qui 23 de fevereiro 11: 13: 34.728029 2017] [mpm_prefork: notice] [pid 17535] AH00163: Apache / 2.4.10 (Debian) configurado - retomando as operações normais [Qui 23 de fevereiro 11: 13: 34.728083 2017] [core: notice] [pid 17535] AH00094: Linha de comando: '/ usr / sbin / apache2'
O que não me parece estar relacionado ao problema, mas talvez eu deva remover esse arquivo de qualquer maneira (embora ele comece bem quando eu removi a seção 443 do arquivo host virtual)
Esta é a mensagem do systemctl:
Falha ao obter a conexão do D-Bus: Nenhum arquivo ou diretório - eu adicionei a seção virtualHost ao meu wordpress.conf para ouvir em 443, o que eu tinha tentado originalmente quando comecei a fazer isso.
Acontece que o problema era este:
SSLCertificate
deveria ter sido
SSLCertificateFile
Esses certificados devem ser adicionados ao seu arquivo VirtualHost e não ao seu arquivo 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>
Também seria bom postar os resultados dos registros de erros, conforme mencionado acima.