Apache 虚拟主机：HTTP 被重定向到默认的 Apache 站点

Question

我已经使用 Apache 虚拟服务器在 VPS 上托管了一个网站，因为我计划稍后在该 VPS 上托管更多站点。在我使用 LetsEncrypt Certbot 在其上安装 SSL 之前，虚拟主机一直正常工作。这样做之后，https://techkernel.org工作正常，但 http 变体http://techkernel.org被重定向到默认的 Apache 网页。虚拟主机配置工作不正常，它被定向到默认的 /var/www/html 目录。

如果您能告诉我如何修复它，以便 HTTP 和 HTTPS 请求都被重定向到 HTTPS 并显示正确的网站，那将非常有帮助。谢谢你。

相关信息：

etc/apache2/sites-available/techkernel.org.conf

<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.techkernel.org

    ServerAdmin webmaster@localhost
    DocumentRoot "/var/www/techkernel.org/public"

    ServerAlias techkernel.org

    # 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
    RewriteEngine on
    RewriteCond %{SERVER_NAME} =www.techkernel.org [OR]
    RewriteCond %{SERVER_NAME} =techkernel.org
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]

</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

var/www/techkernel.org/public/.htaccess

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{SERVER_NAME}/%$1 [R,L]

RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

ls -l /etc/apache2/sites-enabled

lrwxrwxrwx 1 root root 35 Dec 28 11:08 000-default.conf -> ../sites-available/000-default.conf
lrwxrwxrwx 1 root root 38 Jan 21 04:31 techkernel.org.conf -> ../sites-available/techkernel.org.conf
lrwxrwxrwx 1 root root 55 Dec 28 19:46 techkernel.org-le-ssl.conf -> /etc/apache2/sites-available/techkernel.org-le-ssl.conf

ls -l /etc/apache2/sites-enabled

-rw-r--r-- 1 root root 1332 Jul  5  2016 000-default.conf                                                                                                           
-rw-r--r-- 1 root root 6437 Aug  7 10:56 default-ssl.conf                                                                                                           
-rw-r--r-- 1 root root 1574 Jan 19 16:05 techkernel.org.conf                                                                                                        
-rw-r--r-- 1 root root 1613 Dec 28 19:46 techkernel.org-le-ssl.conf

Answer 1

除了您可能在 000-default.conf 中发现的错误之外，您的重写规则中还存在以下问题：

RewriteEngine on
RewriteCond %{SERVER_NAME} =www.techkernel.org [OR]
RewriteCond %{SERVER_NAME} =techkernel.org
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]

应该

RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www\.)?techkernel.org
RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L]

%{SERVER_NAME}如果设置了 UseCanonicalName On，则可能是 VirtualHost 配置中的值。因此，无论访问者使用什么 URI，它都会重定向所有内容。如果这是意图，那么只需删除任何 RewriteCond 并使用

RewriteEngine on
RewriteRule ^/(.*) https://www.techkernel.org/$1 [NC,R=301,L]

如果这是固定的，您可以/应该删除 .htaccess 中有关此的所有条目

RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{SERVER_NAME}/%$1 [R,L]

Answer 2

事实证明 000-default.conf 搞砸了。只有在运行命令后我才注意到这一点apachectl -S。修复它（输入正确的以及一些 URL 重写条件）并安装 apache2 后ServerName，DocumentRoot它reload工作得很好。