Upgrade to ISPConfig 3.1.3 and problem with umask apache

Discussion in 'ISPConfig 3 Priority Support' started by tr909192, Jun 21, 2017.

  1. tr909192

    tr909192 Member HowtoForge Supporter

    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.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    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.
    tr909192 likes this.
  3. pebkac

    pebkac Member

    Having a similar problem after this months patch. Were you able to figure this out?
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    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.

Share This Page