Ubuntu Apache 虛擬主機指向錯誤的目錄？

我正在執行安裝了 Apache 的 Ubuntu 14.04 LTS 伺服器。我設置了 3 個虛擬主機，還有另一個預設伺服器來擷取所有其他未處理的請求。預設伺服器的文件根目錄為 /var/www/。其他 3 個虛擬主機的文件根目錄為 /var/www/html/…/。

我在各自的域名上啟用了所有三個虛擬主機，此時僅可用於本地訪問以進行測試。但是，每當我嘗試訪問三個虛擬主機之一時，我都會立即啟動到預設伺服器的文件根目錄。

這是其中一個虛擬主機的配置，其他的幾乎相同，除了一些顯然必須更改的欄位（文件根目錄、伺服器名稱）。我已經替換了伺服器名稱和文件根目錄，但兩者都是合法的並且存在於伺服器上，如果這很重要的話。

<VirtualHost [example.com]>
DocumentRoot "/var/www/html/[Directory]“
<Directory "/var/www/html/[Directory]“>
   allow from all
   Options None
   Require all granted
</Directory> 
ServerName [example.com] 
</VirtualHost>

這是 default-ssl.conf 文件。

<IfModule mod_ssl.c>
<VirtualHost _default_:443>
   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

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

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

這是 000-default.conf。我不知道為什麼除了這條線之外什麼都沒有顯示。

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

如何讓虛擬主機在訪問時顯示正確的目錄？如果有任何區別，我將在 Ubuntu Server 14.04 LTS 上通過 Webmin 1.750 管理 Apache 伺服器

我在某處讀到需要為預設伺服器指定伺服器名稱，否則它將擷取所有請求，因為它是列表中的第一個伺服器。這是真的？如果是這樣，我該怎麼做？

經過大量的搜尋，我終於找到了原因。

在 Apache 虛擬站點配置中，第一行設置為而不是 ServerName some.domain.com

第一個配置不正確，因為全域指令是 NameVirtualHost *:80

Apache wiki 中的以下段落更深入地解釋了它。

為什麼第一個虛擬主機出錯了？在幾個層面上是錯誤的。最明顯的是第一個塊中使用的 some.domain.com 與 NameVirtualHost 中使用的 *:80 不匹配。另一個是 NameVirtualHost 指的是一個介面，而不是一個域。例如，使用 *:80 表示埠 80 上的所有介面。NameVirtualHost 1.1.1.1:80 表示埠 80 上的地址 1.1.1.1。雖然您可以使用“NameVirtualHost some.domain.com/”組合，但它不會很有意義，通常不被使用……至少沒有被任何有 Apache 管理經驗的人使用。

#httpd 中的報告表明 Webmin 1.510（至少）可能會導致此問題。

我無法發表評論，所以我將其作為答案。我認為在 conf 文件中虛擬主機的 apache 位置很重要。您應該考慮將預設虛擬主機放在頂部，將特定虛擬主機放在底部，因為 apache 在配置選項中選擇最後匹配的任何內容。

引用自：https://serverfault.com/questions/696237