PHP-FPM chroot results in error 500
When enabling chrooted PHP-FPM for a site, it often tries to get files from /var/www/clients/clientX/webXX/web, which should be allowed according to the paths set in the site config, but the /var/www/clients/clientX/webXX is stripped because it is chrooted. This results in quite some broken sites (at least with wordpress) when enabling chrooted PHP-FPM.
I am not sure what would be the best fix - it seems that the webserver tries to get files /var/www and that this is not wordpress specific.