ISPConfig panel not working after updating from wheezy to jessie

Discussion in 'Installation/Configuration' started by rmontagud, Dec 7, 2015.

  1. rmontagud

    rmontagud New Member

    I've just upgraded from wheezy and it seems the virtual host is not working properly and the default virtual host returns a "forbidden" error
  2. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    did you run ispconfig's update.php script after upgrading debian?
  3. rmontagud

    rmontagud New Member

    I've never had to do that after upgrading a distribution, where i can find the script?
  4. rmontagud

    rmontagud New Member

    Turns out there was something really wrong with the base apache configuration files which were not loading the virtual hosts, also inherited virtual host files (valid with apache 2.2 but not with 2.4) never help

    Lesson learned: compare config files from other servers when you think everything is OK
  5. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    Iirc, wheezy had apache 2.2, jessie has apache 2.4, so your old config files should fail after updating. You are seeing expected behavior. :) The update script rebuilds the config files, and will detect you now have apache 2.4, and should create updated versions for you. Similarly, at times you'll change postfix/dovecot/etc. versions and need new config for those.

    As for where to find it, it's in the ispconfig tarball, right beside install.php. If you're not running the latest ispconfig versions (3.0.5p8, I think), you could just run an update to the latest version, see:

    If you're already at the latest version try this (and answer yes to the "reconfigure services" question):
    cd /tmp
    tar xvfz ISPConfig-3-stable.tar.gz
    cd ispconfig3_install/install
    php -q update.php
  6. sjau

    sjau Local Meanie Moderator

    The problem is that the deny/allow method changed from 2.2 to 2.4. So if you have added manually .htacess files or stuff you'll get that error:

    You could try to find if you have according .htaccess files which still specify the old scheme by issuing something like this:

    find /var/www -name ".htaccess" -exec grep -il "order" {} \;
    That should list all .htaccess files in /var/www that contain "order"

Share This Page