Secure Server and second MySQL IRM

*SteveYoung* · 03-25-2011, 05:15 PM

Presently we are using the FQ shared ssl to run a OScommerse store. Looking for a change to that we are testing Wordpress e-commerce solutions.

The website that points to the store is a IRM, we would covert the IRM to a wordpress site with the new 1 IRM allowed to have MySQL.

Things we are thinking about, would the shared ssl work?
If not we would have to order a ssl cert;
Would the ssl be applied to the main site?
Would the ssl be applied to the IRM?\

Thanks to all for your thoughts.

*Melissa* · 03-25-2011, 05:22 PM

Hi Steve,

One of the limitations of IRs is that they cannot have SSL:
http://www.FutureQuest.net/Services/IR/#Limits

Quote:

IRs may not be suitable if:
...
The domain requires SSL. Secure Certs may only be installed on the full package.

For cost recovery and performance reasons, it's not allowed for the Community Servers. However, shared SSL for an IR would be considered under on a Dedicated server (MQS - Managed QuestServer).

**Terra** · 03-25-2011, 05:25 PM

Unfortunately, no - the SSL services would be tied to your primary domain name, even though I can map the SSL handling to any directory in your www tree...

I would recommend converting the IRM to a full package, and then applying Shared SSL services to it...

Another thing you can do is order a VAC ($50.00) which will direct us to switch the primary with the IRM, which will make the IRM primary...

If you don't want to go the VAC route, then you can cancel the primary (which will cancel all IRXes) and reorder a new package with the IRM as primary and then setup the old primary as the new IRM...

*SteveYoung* · 03-25-2011, 05:42 PM

Thanks Melissa and Terra

Tara, this is a parallel effort to find another solution to our problem you were helping me with.

My testing of this new system is on another host, much less expensive and much less reliable, we don't use them for mission critical sites. We will move it once I have it all debugged and understand the package.

I understand, the limitation, I was trying to keep the "family of companies" together on the same package. The IRM is a lightweight as well as the main package compared to other FQ sites we run. I was excited for the one MySQL with a IRM, but I can see how the SSL would complicate this.

Still not sure if the shared cirt will work with the package I am testing, I have more to learn on that package before I will know.

Sounds like "VAC" is a payment for jumbling around the IRM and main package. I will have to consider that. I have a few other (FQ) packages that are lightweights, that could be moved to IRM's, closed then I reopen a new package for the IRM transfer to a full site.

We are not big enough for a dedicated server, but will be some day I am sure.

Thanks for the very prompt response from both of you, this will help in my planning.

*SteveYoung* · 04-19-2011, 11:21 AM

Just for the record on anyone searching for this information. We did move the IRM to a full site.

We had FQ do the shared cert installation. While it provides the encryption, it presents a warning when submitting the order, and transferring the user (customer) to the order page from the cart page.

We have bought a ssl and are going through that process now. Learning a lot but need help, we are going to do a new thread since I am sure others have similar questions or need the knowledge we have gained.