下午好，
因此，我希望我的Web应用程序在Ubuntu 16.04服务器上更安全一些。我正在运行Plex，Torrent客户端，其他一些废话和一个Apache2服务器。 我想建立连接HTTPS，所以我使用了this教程来帮助我安装证书。
我的问题：我无法通过HTTPS公共IP连接到我的Web服务器。 （例如：https://PUBLIC_IP/）
我已在000-default.conf中将重定向设置为始终使用HTTPS，但是我检查了没有重定向的情况，并且我可以访问（http://PUBLIC_IP/），这是合理的，因为它可以运行通过端口80。
但是HTTPS运行在端口443上，据我所知它并没有被防火墙阻止，
UFW很好
我也将它添加到了iptables中。
端口80和443都在路由器上打开。 但是，当我选中“ https://canyouseeme.org/”时，我只能看到80而看不到443
我运行了“ lsof -iTCP -sTCP：LISTEN -P”命令，并列出了443 IS。
$ sudo lsof -iTCP -sTCP:LISTEN -P
apache2 3632根4u IPv6 34173 0t0 TCP *：80（听）
apache2 3632根6u IPv6 34177 0t0 TCP *：443（听）
apache2 3635 www-data 4u IPv6 34173 0t0 TCP *：80（听）
apache2 3635 www-data 6u IPv6 34177 0t0 TCP *：443（听）
apache2 3636 www-data 4u IPv6 34173 0t0 TCP *：80（听）
apache2 3636 www-data 6u IPv6 34177 0t0 TCP *：443（听）
我曾尝试将侦听443更改/添加到ports.conf。
我可以telnet本地主机443。
我无法远程登录PUBLIC_IP 443。
我仔细检查了很多事情，没有犯任何错误。
还尝试了其他一些方法，但据我所知根本没有问题。
随时询问日志和文件。
现在，我不是那种快速提问的人，我在互联网上找不到任何人遇到相同的问题。
换句话说，“帮助”。
如果您认为标题很烂，请告诉我一个更好的标题。我发现这个问题很难描述。
Grtz Mextro
更新 DEFAULT-SSL.CONF
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin [MY_EMAIL]
ServerName [PUBLIC_IP]
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/apache2/ssl/apache.crt
SSLCertificateKeyFile /etc/apache2/ssl/apache.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
# 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>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
更新 PORTS.CONF
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
更新错误日志 错误日志位于/var/log/apache2/error.log.1
[Tue Jan 29 16:17:12.978482 2019] [ssl:warn] [pid 3632:tid 3074254592] AH01906: [PUBLIC_IP]:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Tue Jan 29 16:17:12.979061 2019] [mpm_event:notice] [pid 3632:tid 3074254592] AH00489: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations
[Tue Jan 29 16:17:12.979087 2019] [core:notice] [pid 3632:tid 3074254592] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jan 30 06:25:13.336166 2019] [mpm_event:notice] [pid 3632:tid 3074254592] AH00493: SIGUSR1 received. Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this messag