request for change in how free edition loads virtual hosts

Discussion in 'Feedback/Feature Requests' started by aww, Aug 22, 2008.

  1. aww

    aww Well-Known Member

    With the change in policy after 3.1 in how the free version loads only five hosts from the apache configuration (httpd.conf) I'd like to request a modification that will be more helpful to users.

    Currently when there are more than five in the httpd.conf, litespeed just gives an error and only runs the first five hosts, but doesn't display what's going on and what's actually running. This is very confusing. It's also very difficult to understand how on a cpanel server with just 5 accounts visible, there are actually several more "hidden" - one for each IP a virtual host is tied to.

    I'd like you to consider doing it differently:

    Load ALL the virtual hosts in httpd.conf BUT disable them in the virtual host list (the one with the stop and go buttons that show the status). That will allow the user to see the first five are running but the last few are disabled.

    Then also allow the user to disable other virtual hosts and re-enable other ones - as long as the total stays under 5.

    This will help prevent confusion and also empower the user to have a better experience with litespeed, giving them more control but still staying within your rules.
    Last edited: Aug 22, 2008
  2. mistwang

    mistwang LiteSpeed Staff

    It is not possible for LSWS to tell that is a real vhost or a default vhost for a IP, or a IP based real vhost. You have to manage the order of vhost configuration in httpd.conf manually.
  3. aww

    aww Well-Known Member

    Yes but that's my point, LiteSpeed wouldn't have to determine that, simply show ALL the vhosts in the stop/run list, but only allow 5 to be enabled. By default the first 5 can be enabled and the rest stopped. But if the user wants a different set of vhosts active, they can simply stop the wrong ones running and turn back on the ones stopped, as long the count stays under five.

    Cpanel apparently re-writes httpd.conf at times and moving some vhosts to the end is not guaranteed to keep them there. If they get modified in cpanel, it may put them back on top.
  4. aww

    aww Well-Known Member

    I am running into a problem where Cpanel likes to rebuild httpd.conf from time to time after upgrades, etc.
    It wipes out any re-ordering that I do and messes up the server until I can reorder again.

    How about this simple change in how you count virtual hosts:

    Cpanel makes these kinds of vhosts for fallbacks:

    Could you exclude those from the 5 limit? Anything with a wildcard or IP based?
    Would that be easy enough to do?

    It just drives me crazy because I only have 3 actual domains in use yet cpanel will put them last and puts all those useless fallbacks at the top so they get loaded first by litespeed.

    Thanks for considering!

Share This Page