1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

HTTP restart required for new subdomains?

Discussion in 'Plesk for Linux - 8.x and Older' started by IMspintheweb, Dec 11, 2005.

  1. IMspintheweb

    IMspintheweb Guest


    I was wondering if anybody else is running into this since upgrading to plesk 7.5.4

    Used to be able to access newly created subdomains right after creation, but now we have to restart the apache daemon after every new subdomain, is kinda annoying
  2. phatPhrog

    phatPhrog Guest

    7.5.4 restart

    Yes. We are running 4 PSA 7.5.4 servers and we have the same problems on all of them.

    We thought it was our security causing it, but we re-imaged one server and found the same thing to be true without adding any firewall rules or apps.
  3. blackhowling

    blackhowling Guest

    hi, i think we have the same problem too .
    :D :D :D :D :D :D
  4. phatPhrog

    phatPhrog Guest


    You guys aren't using 1and1.com by any chance?
  5. IMspintheweb

    IMspintheweb Guest

    Re: 1and1

    Yes, do ya think is it a 1 and 1 issue, not plesk?
  6. phatPhrog

    phatPhrog Guest


    I'm inclined to believe so. Am working on it.

    Are you using the 1n1 firewall, the plesk firewall or your own server based firewall?

    1n1 has just made some major changes to their Cisco based firewall so you may look at that. I did and it has solved the problem on one of our servers - (for now)

    We'll see.
  7. cyrus1u1

    cyrus1u1 Guest

    mhm 1and1 told me its a plesk issue, because it executes a wrong command.

    the issue does involve apache restarting in some other cases..

    - password protected directories
    - domain/subdomain creating

    has anybody fixed that? or do i really need to create a cronjob every hour?