Frontpage & Apache on Port 79

Discussion in 'Apache Migration/Compatibility' started by Varial, Apr 22, 2012.

  1. Varial

    Varial Member

    Hi, I'm currently evaluating Litespeed and have it set up on several cPanel servers running CloudLinux.

    I have Apache running on port 79 and Litespeed on port 80 for SSI compatibility. Under this set up Frontpage extensions are not working at all nor can they even be set up through cPanel.

    Attempts to install them in cPanel give the following error:

    Saving .htaccess file: /home/username/public_html/.htaccess
    Error: '' server is not a valid virtual server.

    I have Frontpage extensions enabled in Litespeed's configuration and have also run the commands in but that doesn't actually seem to change the ownership/permissions of the service.pwd file and manually changing it for each user doesn't help to solve the problem either.

    I noticed that I can install FP extensions through cPanel if Apache is completely disabled and Litespeed is running on 80. Will FP extensions not work with Apache running on port 79?
  2. Varial

    Varial Member

    Can anyone shed any light on this? I have a handful of customers using both Frontpage and SSI so getting both working is crucial to switching to Litespeed.
  3. webizen

    webizen Well-Known Member

    pls test it with Apache running on port 80. then switch LSWS to port 80. port 80 requirement is from Frontpage.
  4. Varial

    Varial Member

    It works on port 80. I'm just wondering if it's possible to have Litespeed on 80, Apache on 79 for SSI, and still have Frontpage working?
  5. webizen

    webizen Well-Known Member

    FP should work for whichever listen on port 80. In your case, it is LSWS not Apache.
  6. Varial

    Varial Member

    Frontpage works only when Litespeed is running or only when Apache is running, but not both.

    The problem is when I modify Apache's port to 79 in Tweak Settings in cPanel and set Litespeed's offset to 1, then Frontpage extensions no longer work. Users cannot connect and the extensions cannot be installed. The error message I gave in my first post is given when trying to install them in this scenario.
  7. webizen

    webizen Well-Known Member

    frontpage ONLY works for port 80.
  8. adhp123

    adhp123 Member

    But for ASP.NET, there is a 3rd party Apache modul available.
  9. webizen

    webizen Well-Known Member

    are you talking subdomains for the same account or the domains of other accounts?

Share This Page