locked
Running 2 websites on Vail RRS feed

  • Question

  • I just installed Vail the other day, and was just monkeying around with IIS trying to get two websites running at the same time.

    I created a new website named public in IIS and bound it to port 80, and just removed the binding for port 80 from the default website. so now browsing to http://example.homeserver.com gives me the public website, and https://example.homeserver.com goes to the remote web access login page. Pretty much exactly what I was hoping for.

    I'm just wondering if that is going to break anything. I know all of the remote web access stuff goes through port 443 - Is there anything that actually uses port 80 that doing this will break? The alternative to doing it this (easy) way is to give the local area connection 2 IP addresses, binding one to each site, and using the "virtual server" option on the router to point a different public port to each IP, but that would still be less ideal because you would have to go to example.homeserver.com:8080 or whatever.

    Also, after setting this up manually I'm assuming that running any of the network-related wizards could very well undo all my changes, but do you suppose just installing updates would change any of these settings?

     

    Saturday, August 21, 2010 6:30 PM

Answers

  • I just installed Vail the other day, and was just monkeying around with IIS trying to get two websites running at the same time.

    I created a new website named public in IIS and bound it to port 80, and just removed the binding for port 80 from the default website. so now browsing to http://example.homeserver.com gives me the public website, and https://example.homeserver.com goes to the remote web access login page. Pretty much exactly what I was hoping for.

    I'm just wondering if that is going to break anything. I know all of the remote web access stuff goes through port 443 - Is there anything that actually uses port 80 that doing this will break? 

    First, everything you are trying to do is unsupported (just so you know).  As for whether it would break anything, my guess is no.  However, since you've already done the leg-work, you should be able to determine that easily enough yourself.  Try everything Vail has to offer and see if everything continues to function.

    The alternative to doing it this (easy) way is to give the local area connection 2 IP addresses, binding one to each site, and using the "virtual server" option on the router to point a different public port to each IP, but that would still be less ideal because you would have to go to example.homeserver.com:8080 or whatever.

    Also, after setting this up manually I'm assuming that running any of the network-related wizards could very well undo all my changes, but do you suppose just installing updates would change any of these settings?

    As there are no updates for Vail (and presumably won't be for sometime since it's still in beta), there is no way of knowing.  I can tell you though that any "unsupported" changes made in v1 (i.e. replacing the default picture on the website) were reverted back to the original settings after any Power Pack was installed.
    Saturday, August 21, 2010 8:15 PM
    Moderator