Dear, after an upgrade from ISPConfig 3.1.2 to ISPConfig 3.1.3 we have got a problem with apache umask. Basically with ISPConfig 3.1.2, website with fast-cgi create file with correct permission (644) after the upgrade for not apparently reason the file are created with 600 permission. That's a problem because they are not visibile via web in that way. We have found a workaround forcing umask 002 on (/etc/apache2/envvars) but this was not required before that upgrade. Someone can put us in the correct directions on why happen that strange behaviour? Thank you.
There have been no changes in that area from 3.1.3 to 3.1.2 as far as I know. What you can do is that you compare a fcgi starter file from a working site with one of a site that does not work.
No, not reproducible on any system. Especially as Umask is not set by ISPConfig, which means that the admin of that system or another software must have altered the default umask.
