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

URL of a site appears wrong

Discussion in 'Plesk for Windows - 8.x and Older' started by bmorejon, Jun 17, 2004.

  1. bmorejon

    bmorejon Guest

    0
     
  2. paulwilson159

    paulwilson159 Guest

    0
     
    This [should] be resolved in the version 7 release, but in the meantime, here is a workaround.

    Remote access to the server and go into the IIS control panel (MMC)

    Click on Web sites to highlight it.
    Right click and select "New Site"
    Start the wizard
    Give the site a name - in this instance, try domain.suffix (no www.)
    Set the IP address to that of your server (do not use ALL UNASSIGNED) - port 80 is chosen as default.
    Set the host header as www.domain.suffix
    Now you choose the directory where the site is based - click browse and go to C:\Inetpub\vhosts\domain\httpdocs
    Now set permissions for access.
    Click Next to finish

    Now right click on your new site and go to properties
    Go to the Home Directory tab
    Set the Application pool to PSASystemAppPool
    Now click on the Configuration button
    Choose Options and be sure to enable the asp parent paths (important)

    Finally go to Web site tab, click Advanced and add the domain.suffix alias to the IP address and port 80 (www.domain.suffix is there already, so adding domain.suffix enables both to be seen in the browser)

    The web site will now use IIS mapping directly, allowing the proper path to be seen.

    You will also need to create virtual directories in the IIS version site for the webstat folders - these can be mapped back to the correct Plesk folders - otherwise your stats will not work from the control panel.
     
  3. bmorejon

    bmorejon Guest

    0
     
    Once I do this, I will be free of this problem ?
    or I have to do this to all web sites ?
     
  4. paulwilson159

    paulwilson159 Guest

    0
     
    Heres the bad news - you will need it for every site - specifically the ones that use ASP pages. Basic html sites would be just as well left alone.

    This is a temp workaround - hopefully version 7 will eliminate this bug.
     
  5. bmorejon

    bmorejon Guest

    0
     
    Thank you for the help paulwilson159

    I will wait for the 7. :)
     
Loading...