Upgrade to 2.2.6 puts # Redirect # NOT SUPPORTED

Discussion in 'Installation/Configuration' started by ppettigrew, Aug 21, 2006.

  1. ppettigrew

    ppettigrew New Member

    Hi,

    We have just completed a successful upgrade from 2.2.5 to 2.2.6, but noticed the strangest thing.....

    For each site we provide Domain/URL forwarding for, we have had the Apache (Optional) directive entered thus:
    Redirect / http://www.someotherdomain.com/

    Since the upgrade, these have all been changed to:
    # Redirect / http://www.someotherdomain.com/ # NOT SUPPORTED!

    We seem to have fixed the issue, by manually correcting each site back to the original Redirect directive.

    Any idea what caused this? We would not like to have to manually do this each time we upgrade again....

    Cheers and thanks always for a brilliant piece of software.

    Paul
     
  2. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Please make sure the Apache module configuration hasn't changed. ISPConfig runs
    Code:
    httpd -t
    to find out if your custom directives are supported, and if the command returns an error, your directives are commented out.
     
  3. lorello

    lorello New Member

    If httpd -t return an error, ISPConfig comment ALL custom directives, in all sites, is this correct?

    :confused: So it's very dangerous give this option to reseller... if one reseller make some mistake in one of his virtualhosts, he damage all virtualhosts... and he can't repeair the damage :confused:
     
  4. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    If I remember correctly, ISPConfig tests the directives for every website independently, not the whole config file at once.
     

Share This Page