无法让 Symfony 在生产服务器上工作

Question

编辑：对于遇到同样问题的人，认真地说，只需创建一个子域并将其定向到 symfony 网络目录即可。 Symfony 的 url 重写系统显然是围绕 something 的根目录构建的。其他任何事情都不值得头疼。

过去两天我一直在尝试让一个新的 Symfony 项目在我们的服务器上运行。我安装项目没问题，但是当我尝试转到 example.net/symfony/web/app_dev.php 时，我的网站出现 404 page not found 错误，而不是 Symfony，与 app.php 相同。

这是一个如此简单的问题，但它却让我头疼了好几个小时，一点头绪都没有。

我没有为我们的网站或新的 Symfony 项目对我们的 .htaccess 文件做任何花哨的事情。

Symfony .htaccess：

# Use the front controller as index file. It serves as a fallback solution when
# every other rewrite/redirect fails (e.g. in an aliased environment without
# mod_rewrite). Additionally, this reduces the matching process for the
# start page (path "/") because otherwise Apache will apply the rewriting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex app.php

# By default, Apache does not evaluate symbolic links if you did not enable this
# feature in your server configuration. Uncomment the following line if you
# install assets as symlinks or if you experience problems related to symlinks
# when compiling LESS/Sass/CoffeScript assets.
# Options FollowSymlinks

# Disabling MultiViews prevents unwanted negotiation, e.g. "/app" should not resolve
# to the front controller "/app.php" but be rewritten to "/app.php/app".
<IfModule mod_negotiation.c>
    Options -MultiViews
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On

    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #   following RewriteCond (best solution)
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule ^ - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule ^ %{ENV:BASE}/app.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the start page to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /app.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

网站 .htaccess：

RewriteOptions inherit

# BEGIN WPSuperCache
# END WPSuperCache

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} ^/appone/?.*$
RewriteRule ^(.*)$ https://example.net/$1 [R=301,L]

RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} ^/apptwo/?.*$
RewriteRule ^(.*)$ https://example.net/$1 [R=301,L]

RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} ^/appthree/?.*$
RewriteRule ^(.*)$ https://example.net/$1 [R=301,L]

我在 Apache error_log 中收到这些错误：

[Thu Jan 14 07:06:24.920671 2016] [:error] [pid 8852] [client 99.99.999.9:99999] SoftException in Application.cpp:431: Mismatch between target GID (512) and GID (20) of file "/home/user/public_html/symfony/web/app.php"
[Thu Jan 14 07:06:24.920715 2016] [core:error] [pid 8852] [client 99.99.999.9:99999] End of script output before headers: app.php
[Thu Jan 14 07:06:34.560027 2016] [:error] [pid 8503] [client 99.99.999.9:99999] SoftException in Application.cpp:431: Mismatch between target GID (512) and GID (20) of file "/home/user/public_html/symfony/web/app_dev.php"
[Thu Jan 14 07:06:34.560079 2016] [core:error] [pid 8503] [client 99.99.999.9:99999] End of script output before headers: app_dev.php
[Thu Jan 14 07:09:19.556406 2016] [:error] [pid 8852] [client 99.99.999.9:99999] SoftException in Application.cpp:422: Mismatch between target UID (501) and UID (1337) of file "/home/user/public_html/symfony/symfony_demo/web/app.php"
[Thu Jan 14 07:09:19.556452 2016] [core:error] [pid 8852] [client 99.99.999.9:99999] End of script output before headers: app.php

如果您需要任何其他信息，我会尽力提供。感谢您的帮助。

Answer 1

我的代表仍然太低，无法发表评论，所以我会发布答案。

您的 htaccess 与 404 问题无关。

如果您使用 Debian，请转到 /etc/apache2/sites-available 并为 Symfony 创建一个页面，就像这里显示的 http://symfony.com/doc/current/cookbook/configuration/web_server_configuration.html 。

确保定义正确的 symfony 文件夹位置，否则它将不断返回 404 错误。

它应该看起来像这样

<VirtualHost *:80>
    ServerName YOURDOMAINNAME.DOMAIN
    ServerAlias www.YOURDOMAINNAME.DOMAIN

    DocumentRoot FULL_SYMFONY_PATH
    <Directory FULL_SYMFONY_PATH>
        AllowOverride None
        Order Allow,Deny
        Allow from All

        <IfModule mod_rewrite.c>
            Options -MultiViews
            RewriteEngine On
            RewriteCond %{REQUEST_FILENAME} !-f
            RewriteRule ^(.*)$ app.php [QSA,L]
        </IfModule>
    </Directory>

    # uncomment the following lines if you install assets as symlinks
    # or run into problems when compiling LESS/Sass/CoffeScript assets
    # <Directory /var/www/project>
    #     Options FollowSymlinks
    # </Directory>

    ErrorLog /var/log/apache2/project_error.log
    CustomLog /var/log/apache2/project_access.log combined
</VirtualHost>

此配置还禁用 htaccess。

将此配置命名为 YOURDOMAINNAME.conf，然后将其输入到控制台 a2ensite YOURDOMAINNAME.conf。

我认为还有一些额外的步骤，但我不在我的普通计算机上，如果它不起作用，请告诉我。

对了，现在我想起来了，你需要使用 a2enmod rewrite 这一行来启用 mod_rewrite，然后重启 apache。

Answer 2

不确定它是否有帮助，但尝试将 DocumentRoot 更改为 symfony/web 目录（因此 web 文件夹是站点的根目录）？