As dawud says there should be no
" around the match block, whilst sshd is happy to start without complaint, with the
" when you try to connect it drops the connection.
" are a typo in your question then there are other things to check. First check you logs and see if there are any relevant messages that are useful. Unfortunately without knowing what OS the server is running we can't be much more specific than that about which ones.
Check that the ownership and permissions on /var and /var/www are suitable for a chroot environment.
It could be SElinux, again check your logs (audit.log perhaps) for suspicious
avc: denied messages. There are a couple of SELinux boolean values that may be helpful if this is the case,
ssh_chroot_full_access. The former would seem most appropriate try
setsebool ssh_chroot_manage_apache_content true
and if this works make it permanent with
setsebool -P ssh_chroot_manage_apache_content true