Symfony framework install 406 Not Acceptable Error w/CPanel & WHM


So I am trying to get Symfony working on my server by following these install instructions.

I got to the part where I ran this command in console in the directory where I wanted the framework to be installed.

symfony new my_project_name

I then followed these instructions to set my web root directory to /web as I believe I’m supposed to do?

It installed all the files correctly since I can see them in the folder. I made sure to restart apache and I’m positive document root is in the correct location.

Once I did this I was supposed to be able to test the installation, but nothing seems to happen except that 406 error?

This is the exact error I get.

An appropriate representation of the requested resource /app.php could not be found on this server.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

I’m not sure what else to do.

Please note, that since I’m using CPANEL I can’t change the virtual host configurations of apache if that is the issue, so I’m looking for a CPanel specific answer. Thank you!


Okay so I finally figured out what to do, I had 2 problems. Because I installed as the ‘root’ user I had to run the following command on the symfony installation.

chown -R devdistribution:devdistribution .

In my case, my username is devdistribution but you would just put your own. Make sure to do this on the top level not just the /web folder.

I knew this was one of the errors because the apache log said something along these lines

Mismatch between target UID (520) and UID (501) of file “/home/devdistribution/public_html/distribution_tech/web/app.php”

This fixed the 500 error, but not the 406. To fix the 406 error you need to login into WHM and type modsecurity to find it in the search field.

go to the configuration option for it, you will see this.

Rules Engine SecRuleEngine 
This setting controls the behavior of the rules engine.
 Process the rules.
 Do not process the rules.
 Process the rules in verbose mode, but do not execute disruptive actions.

Select ‘Do not process the rules’. Then save at the bottom. This fixed the issue for me and I was able to see the opening symfony screen!

However, this I’m sure leaves security vulnerabilities now…so I still need help on the proper way to handle mod security with symfony in this case if anyone knows? I’ll make a separate question for this.

Answered By – Joseph Astrahan

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published