Веб-сервер Apache2 всегда обслуживает HTTP, хотя у меня настроен только SSL

247
Brian

Я пытаюсь разместить веб-сервер SSL Apache2 в Ubuntu 16.04 в домене mturk.bitasy.me, но у меня есть основания полагать, что сервер лжет мне, где-то, по крайней мере. Я создал два файла в каталоге sites-enable, один для HTTP и один для HTTPS. Они размещены ниже. По какой-то причине http один работает нормально (если вы заходите на сайт, вы видите, что он работает), но https не загружается, независимо от того, что я делаю. Я даже зашел так далеко, что переместил файл конфигурации http и установил SSL только на веб-сервере, но даже в этом случае HTTP (как-то) работает, а SSL (как-то) все еще не размещается. Это тот случай, даже если я полностью удалил строку Listen 80 из ports.conf и заменил ее на Listen 443. Я проверяю, чтобы сервер перезагружался каждый раз ( sudo service apache2 restart) и при запуске (apache2 -S) результат следующий. Это буквально показывает мне, что он не слушает порт 80, но это единственный порт, где отображается сайт! Я также выложу журнал ошибок ниже, в котором нет ничего полезного. Моя интуиция говорит, что каким-то образом сервер не обновляется, когда я перезагружаю его, но печать -S просто делает это невозможным. Дело не в том, что работают как-то два сервера, потому что, когда я его прекращаю, HTTP-сайт действительно становится недоступным.

$:apache2 -S  VirtualHost configuration:  *:443 mturk.bitasy.me (/etc/apache2/sites-enabled/default-ssl.conf:2)  ServerRoot: "/etc/apache2"  Main DocumentRoot: "/var/www/html"  Main ErrorLog: "/var/log/apache2/error.log"  Mutex ssl-stapling-refresh: using_defaults  Mutex ssl-stapling: using_defaults  Mutex ssl-cache: using_defaults  Mutex default: dir="/var/lock/apache2" mechanism=fcntl  Mutex watchdog-callback: using_defaults  PidFile: "/var/run/apache2/apache2.pid"  Define: DUMP_VHOSTS  Define: DUMP_RUN_CFG  User: name="www-data" id=33 not_used  Group: name="www-data" id=33 not_used 

Конфигурация сайта SSL (в настоящее время не включена):

<VirtualHost *:80> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com  ServerAdmin webmaster@localhost DocumentRoot /var/www/html ServerName mturk.bitasy.me  # 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 $/error.log CustomLog $/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 </VirtualHost> 

Конфигурация сайта HTTPS (указана как активная, но нет)

<IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost  DocumentRoot /var/www/html ServerName mturk.bitasy.me # 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 $/error.log CustomLog $/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 /home/ubuntu/site.crt SSLCertificateKeyFile /home/ubuntu/mturkhost.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 /home/ubuntu/GandiStandardSSLCA2.pem  # 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  </VirtualHost> </IfModule> 

Еще одна неудачная попытка SSL:

<VirtualHost *:443> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com  ServerAdmin webmaster@localhost DocumentRoot /var/www/html ServerName mturk.bitasy.me SSLEngine on SSLCertificateFile /home/ubuntu/site.crt SSLCertificateKeyFile /home/ubuntu/mturkhost.key SSLCertificateChainFile /home/ubuntu/GandiStandardSSLCA2.pem  # 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 $/error.log CustomLog $/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 </VirtualHost> 

Файл ошибки:

[Thu Sep 06 03:24:22.411215 2018] [mpm_event:notice] [pid 7032:tid 139914827044736] AH00489: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations [Thu Sep 06 03:24:22.411284 2018] [core:notice] [pid 7032:tid 139914827044736] AH00094: Command line: '/usr/sbin/apache2' 
0
Я голосую, чтобы закрыть этот вопрос как не по теме, потому что невозможно воспроизвести jww 5 лет назад 3

1 ответ на вопрос

0
Brian

Как и в случае с отладкой, я понял проблему после нескольких часов безуспешно, сразу после того, как обратился за помощью.

Я использую сервер Amazon Lightsail, брандмауэр которого по умолчанию настроен на прием только соединений через порты 20 и 80 для SSH и HTTP. Мне нужно было вручную разрешить SSL-соединения через порт 443.

Похожие вопросы