Не удается заставить Symfony работать на производственном сервере

EDIT: для тех, кто имеет одну и ту же проблему, серьезно, просто создайте поддомен и направьте его в веб-каталог symfony. Система перезаписи URL-адресов Symfony, очевидно, построена вокруг того, что находится в корневом каталоге чего-то. Все остальное не стоит головной боли.

Я пытался за последние два дня получить даже свежий проект Symfony для запуска на нашем сервере. Я устанавливаю проект без проблем, но когда я пытаюсь перейти к example.net/symfony/web/app_dev.php я получаю ошибку 404 страницы для моего сайта, а не для Symfony, то же самое с app.php.

Это такая простая проблема, но это вызвало у меня частые боли в голове без малейшего движения.

Я не делаю ничего интересного с нашим файлом.htaccess для нашего сайта или для нового проекта Symfony.

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

Если вам нужна дополнительная информация, я сделаю все возможное, чтобы обязать вас. Спасибо за помощь.