Symfony 3.4 Apache权限异常：WebServer无法写入目标文件夹

Let’s work through this permission problem together—you’re right that this is an Apache/filesystem permission mismatch, and we can get it sorted with a few targeted steps.

First: Correct the Directory Ownership & Permissions #

Your current directory has root as the owner, which is why Apache (running as www-data) can’t write to it. Let’s fix that first:

1. Set the correct owner and group for the target directory (and all its contents):

   sudo chown -R www-data:www-data /var/www/html/site/public/front/cms/explanatory_rubric
   

   This ensures the Apache process user (www-data) owns the directory, which is required for writing.

2. Apply secure, functional permissions
   Instead of using overly broad 777 permissions, use a more secure setup:

   sudo chmod -R 775 /var/www/html/site/public/front/cms/explanatory_rubric
   

   The 775 gives read/write/execute to the owner and group, and read/execute to others. If you want even finer control, use ACLs (recommended for shared environments):

   sudo setfacl -R -m u:www-data:rwx /var/www/html/site/public/front/cms/explanatory_rubric
   sudo setfacl -R -d -m u:www-data:rwx /var/www/html/site/public/front/cms/explanatory_rubric
   

   The second command ensures any new files created in the directory inherit the same permissions.

Second: Update Apache VirtualHost to Use Modern Syntax #

Your current config uses Apache 2.2-style Order Allow,Deny syntax, which might cause issues in Apache 2.4+. Replace those blocks with:

<IfModule mod_ssl.c>
  <VirtualHost *:443>
    ServerName www.mysite.com
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    <Directory /var/www/html/site/public>
        AllowOverride All
        Require all granted
    </Directory>

    <Directory /var/www/html/site/public/front/cms/explanatory_rubric>
        AllowOverride All
        Require all granted
    </Directory>

    # Don't forget your SSL certificate directives here!
    SSLCertificateFile /path/to/your/cert.pem
    SSLCertificateKeyFile /path/to/your/key.pem
  </VirtualHost>
</IfModule>

Then restart Apache to apply changes:

# Debian/Ubuntu
sudo systemctl restart apache2

# RHEL/CentOS/Fedora
sudo systemctl restart httpd

Third: Check for SELinux Restrictions (RHEL/CentOS/Fedora) #

If you’re on a Red Hat-based system, SELinux is likely blocking Apache from writing to the directory—even if filesystem permissions are correct.

1. Test temporarily by disabling SELinux (just to confirm it’s the issue):

   sudo setenforce 0
   

   Try uploading an image now. If it works, SELinux was the culprit.

2. Set a permanent SELinux rule to allow Apache write access:

   sudo semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html/site/public/front/cms/explanatory_rubric(/.*)?"
   sudo restorecon -Rv /var/www/html/site/public/front/cms/explanatory_rubric
   

   This marks the directory as a valid write location for Apache, and restores the SELinux context to apply the rule.

Fourth: Verify PHP Configuration (Optional) #

In rare cases, PHP’s open_basedir setting might restrict access to the directory. Check your php.ini (or virtual host-specific PHP config) to ensure the path /var/www/html/site/public/front/cms/explanatory_rubric is included, or that open_basedir isn’t overly restrictive.

Final Check #

After applying these steps, clear Symfony’s cache (for production):

sudo php /var/www/html/site/bin/console cache:clear --env=prod

Then test uploading an image again—this should resolve the write error.

内容的提问来源于stack exchange，提问作者Al Ex