Domain Add-on with two stores and using SSL for both
Posted: Wed Jul 20, 2011 8:30 am
A while back I posted about how to use two different themes with the same store backend... and I got some good advice here: viewtopic.php?f=42&t=14506&p=62502&hili ... ssl#p62502
Basically, we have two domain names that use the same store. The code on that page helped me to set it up so that the theme changed based on the domain name.
An issue that has come to light is that the SSL certificate does not work for the second domain. Since the first domain's SSL certificate was already applied to the store, the second SSL could not also be applied -- because, in the end, both domains are pointing to the same ip address.
The host (Rackspace) has advised me that the best route to take would be to have two separate websites with two ip addresses. However, what is nice about our current situation (2 domains, 1 backend) is that if the main store is updated, so is the second store. The client doesn't need to update two stores.
The obvious next question is -- why not have two store installations that share the same database? I believe that we actually tried pursuing this a while back and this was not possible, because of AC's setup. However, if this seems incorrect to anyone, please let me know. Rackspace did also tell me that there are SSL certificates for multiple domains, but they do not support them, as they have a tendency to mess things up (which we'd like to avoid, too).
Ideally, it would be nice to find a workaround to keeping the website(s) as they are now -- and just get the SSL to work. Anyone have experience with this?
Basically, we have two domain names that use the same store. The code on that page helped me to set it up so that the theme changed based on the domain name.
An issue that has come to light is that the SSL certificate does not work for the second domain. Since the first domain's SSL certificate was already applied to the store, the second SSL could not also be applied -- because, in the end, both domains are pointing to the same ip address.
The host (Rackspace) has advised me that the best route to take would be to have two separate websites with two ip addresses. However, what is nice about our current situation (2 domains, 1 backend) is that if the main store is updated, so is the second store. The client doesn't need to update two stores.
The obvious next question is -- why not have two store installations that share the same database? I believe that we actually tried pursuing this a while back and this was not possible, because of AC's setup. However, if this seems incorrect to anyone, please let me know. Rackspace did also tell me that there are SSL certificates for multiple domains, but they do not support them, as they have a tendency to mess things up (which we'd like to avoid, too).
Ideally, it would be nice to find a workaround to keeping the website(s) as they are now -- and just get the SSL to work. Anyone have experience with this?