[英]Can't get Symfony to work on production server
編輯:對於有相同問題的人,請認真對待,只需創建一個子域並將其定向到symfony Web目錄即可。 Symfony的url重寫系統顯然是建立在某物的根目錄上的。 其他任何事情都不值得頭痛。
在過去的兩天里,我一直在努力讓一個新的Symfony項目在我們的服務器上運行。 我安裝項目沒問題,但是當我嘗試轉到example.net/symfony/web/app_dev.php
,我的站點(而非Symfony)遇到404頁面未找到錯誤,與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
如果您需要任何其他信息,我們將盡力。 感謝您的幫助。
我的代表仍然很少,只能發表評論,因此我將發布答案。
您的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。
不確定是否有幫助,但是嘗試將DocumentRoot更改為symfony / web目錄(因此,web文件夾是站點的根目錄)?
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.