Sounds like an internet terror meme, but it's not.
I debated posting this here or in the Help/Advice forums and figured since more techie types post here I'd probably get a better response.
Microsoft released their preview of Home Server Veil on Monday and I've since fired it up and gotten it running a secon machine at home. I also have a pre-existing Home Server at home.
I want the websites to co-exist.
I currently use the primary one and have several pictures and such linked to it from the outside world, I fear it too complicated for me to currently migrate the entire site tot he new system due to the add-ins I use, but I would love to take the new setup and have it move forward. I love it's features and want to use them to share pictures and movies with my family.
The problem is that both sites use SSL, and both sites use a login feature that requires you to authenticate against the host. I've read a few different things online on how to try to get it working but none of them seem to relate to having
two SSL based websites.
Both sites are operating from *.homeserver.com realm, which I read should be do-able, just don't know how to get it done.
Any help/advice would be appreciated.
Posts
It'd be it's own machine (or one of the other machines) that'd decide which website to load based on what it received. I have no knowledge on how to set them up, though.
Here's what a quick google said about changing ports for whs.
This would be true, if not for the SSL certs. Based on what I've read SSL certs get read above all else, it's a security measure... And I'm trying to bypass it... Reverse proxy sounds good, I'll look into that.
any other thoughts?
Movie Collection
Foody Things
Holy shit! Sony's new techno toy!
Wii Friend code: 1445 3205 3057 5295
Movie Collection
Foody Things
Holy shit! Sony's new techno toy!
Wii Friend code: 1445 3205 3057 5295
That's why I said you would have to use ip:port to specify which machine you wanted on the one that you change from default rather than just ip. It seems like it wouldn't be much different than having to change ports because an isp has the standard ones blocked. Another quick google shows it can be done. Check these links
http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/
http://www.myhomeserver.com/?page_id=23
But, of course, I'm going off other things I've had trouble with in the past since I've never used WHS so I'm all out of other ideas. Good luck!
beta.homeserver.com -> yourip:81
alpha.homeserver.com -> yourip:80
That'd work too. But that's pretty much a reverse proxy situation that's handled by homeserver.
However just having them on different port numbers as forwarded by a router won't accomplish anything.
For instance, yourip:80 & yourip:81 (alpha and beta servers respectively). Let's say you point your nameserver for both of these (domain1.com and domain2.com) to your ip address. Nameservers really can't differentiate IP:port combos. So visiting domain1.com will bring you to the alpha server, visiting domain2.com will still bring you to the alpha server.
domain1.com:81 will bring you to the beta server. I understand what you're saying but, without a reverse proxy (and in your examples it seems like homeserver handles that fine it looks like?) you won't be able to accomplish anything.
Just in case someone else tries this and figures "hey with my own domains I should be able to mimic what homeserver has set up!"