first steps with ISPConfig 3... help please

Discussion in 'Installation/Configuration' started by manarak, May 12, 2009.

  1. manarak

    manarak Member

    Ok, I have installed ISP3 on my Debian Lenny box.

    It is sitting on my home network at the address

    Please consider that I am not familiar with either ISPconfig 2 or 3. I am a noob.

    I can login to ISP3 at
    and phpmyadmin works at

    When I call, it says:
    Is that normal behavior?
    BTW, I use a clean install of Debian Lenny, why does it say Fedora?

    If I call it just says "It works!"

    Then I try to setup a website.

    I added a client.
    I added a site (dummy domain), using * as IP.

    If I understand correctly, this should cause the server to show that site per default whenever the Server's IP is called from a browser?

    But it doesn't work. I still get "bad request" if I call

    Who can help me to make the default site appear please?
  2. manarak

    manarak Member


    I changed the * as an IP setting in the website settings page, then I restarted apache.

    same same

    then I deactivated the website throught the same interface and reactivated it.
    then I restarted apache again.

    the bahavior changes. the "bad request" error page is now styled in ISPC style. it still says "bad request" but with "error 400"

    So there seems to be a small bug that settings are not properly written to DB unless the site is deactivated and reactivated.

    But my problem remains, the site still doesn't appear.
  3. rdv25772

    rdv25772 New Member

    What is the content of your apache default file? It should be in the /etc/apache2/sites-available directory.

    Did you follow the instructions in the perfect setup Howto of Falko or did you do anything else?
  4. manarak

    manarak Member

    Hi Richard

    here is what the default file says:

    Yes, I followed Falko's tutorial exactly.
    I just skipped the parts on fstab and jailkit

    And I added mod_security

    BTW, I noted that the www directory is in /var ?
    What the hell does it do there? Shouldn't it be under /home?
    I assigned 200 Gigs to /home !!
  5. manarak

    manarak Member


    I just retried with and I do get the "welcome to your website" page.

    Shouldn't port 80 be default for http: ?
    What is wrong?
  6. rdv25772

    rdv25772 New Member

    It seems to be ok. I don't have the problems like you.

    I believe the /var/www directory is the default directory for Debian. What you can try is to move the content of the www-directory to /home and create a symbolic link for /var/www.

    The port 80 is the default for http. I don't know what is wrong. It seems you doing the right thing. Anyone else who can help in this?
  7. manarak

    manarak Member

    Hi Richard, and thanks for looking into that.

    I found some wierd things in the mod_security log.
    Apparently, mod_security is causing the malfunction.
    I'll disable it and check the rulesets.

    there are still some topics I'd like to discuss with ISPConfig pros:

    * location of www*
    Thanks for the hint about the link to /home, but I wonder what will happen when /var is full ?
    Will the link from /var to /home still work if /var is full?
    (I want the websites to work, even when a bug caused my logs to explode).

    * /tmp *
    I mounted /tmp with noexec, nosuid to further secure my setup, but I see the upload tmp is set separately for each web under var/www/client1/web1/tmp or something like that.
    Is it safe to assume I just need to change the vhost template and set it there to /tmp ?
    Is that even useful? Will it be more secure?

    * mod_dosevasive *
    I have mod_dosevasive installed on my other box.
    After some years I still can't say if it is useful or not?
    What's your opinion?

    * RAID and mdadm *
    I've got hardware RAID on the box (RAID 1 with two hot swap HDD), and there is only one HDD showing up in the operating system.
    ISPConfig says RAID status can't be shown because mdadm is not installed.
    Should I install mdadm? Is it useful with hardware RAID?

    >> I'm sure I'll have more questions soon :)) Thank you
  8. manarak

    manarak Member

    ok, found the mod_security rule responsible: in anomalies, it checks that the HOST header is not an IP Adress...

    Now that's a useful rule...

    The site works now.
  9. manarak

    manarak Member

    does anyone know the answers?

Share This Page