--------------010808000608000609020602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
We are the hosting company, and we've been running Miva stores on
Windows based servers without any problems for over 3 years now. We
have not upgraded our version of Miva or Empressa because the costs are
exorbitant (as are the support offerings - which used to be free to
licensed owners prior to the compiled versions having been introduced).
Needless to say, we have since found better, more cost effective
e-commerce solutions, and will no longer be purchasing any new Miva
licenses. We do have a responsibility to cater to our existing Miva
users, however, .. which is why I've posted my inquiry to the list.
We are using shared SSL because the control panel software we have
carefully selected and invested thousands of dollars in does not allow
for it. We are not nearly as upset about this as you seem to be, ..
though we appreciate your concern :) Having gotten all that out of the
way, .. do you have any technical advice to offer? Or were you simply
trying to pitch me on switching to your Miva hosting services?
- yvan
WolfPaw Computers - Webmaster wrote:
>*** OFFLIST REPLY ***
>
>I'd have several concerns here, the first being why host on Windows?
>Miva was designed to run on Linux, and yes - while there have been ports
>for the Windows OS Platform, it has never performed well or been stable
>there. Not from any fault of the Miva software, but from severe
>limitations in the Windows Server OS's like memory leaks and poor
>resource utilization.
>
>Another would be why you migrated and have not upgraded Empresa from
>v3.9301 to the more secure and stable v3.97x
>
>I would be very concerned about your SSL situation. There is absolutely
>NO REASON you cannot use your own SSL certificates for each domain. If
>you're current host does not know how to properly configure each virtual
>host to allow its own SSL, I would leave that host ASAP for someone
>that actually knows what they are doing.
>
>Those are some serious concerns. I'd be thinking about moving my
>business to a Miva Hosting Specialist.
>
>Vic Vega
>WolfPaw Computers
>Miva Merchant Hosting Specialists
>"Put the power of the pack to work for you!"(sm)
>Miva Standard Hosting Partner - OpenUI Premier Partner
>FREE MerchantHowTo.com Basic Tutorial Subscription with each hosting
>account! A $49 value!
>http://tinyurl.com/48nmu
>
>Ph: 1 (866) WOLFPAW
>www.wpcomp.com
>
>
>
>
>>-----Original Message-----
>>From: [email protected]
>>[mailto:[email protected]] On Behalf Of Yvan Gagnon
>>Sent: Tuesday, April 19, 2005 9:20 AM
>>To: [email protected]
>>Subject: [mru] Server 2003 / Miva v3.02 / Shared SSL
>>
>>
>>We recently migrated to Windows Server 2003, and had to transplant a
>>couple of our Miva merchant storefronts to the new box (We are using
>>Miva Merchant version 3.02, with version 3.9301 of the Miva Engine /
>>Empressa).
>>
>>Our new web server configuration requires that we use shared
>>SSL, rather
>>than having individual certificates for each of our clients.
>>So we've
>>designated a single domain for this purpose, and have successfully
>>installed the SSL certificate for it. This of course
>>requires that we
>>set up virtual directories for each domain that requires SSL. For
>>example, ..
>>
>>If the domain "www.thedomainname.com" requires SSL, .. we go into IIS
>>and add a new virtual directory underneath the domain we've
>>designated
>>for SSL (ie: www.ssldomain.com) which points to the root directory of
>>the website that requires SSL. The resulting url would typically be
>>something like ...
>>
>>
>>
>https://www.ssldomain.com/thedomainname
>
>The virtual directory setup (I believe) also requires that we add the
>necessary settings underneath the "Miva Engine" tab in IIS. This
>involves us specifying the data directory, as well as specifying paths
>to any needed commerce libraries.
>
>So once we get one of these virtual directories set up, the next step is
>
>for us to go in to the Miva Admin for that domain and update the SSL
>urls with the new one we've just created ( Secure URL to Miva Merchant,
>Secure URL to Administration, and Secure Base URL for Graphics ).
>
>However, .. it is not working. I am getting the dreaded MER-MER-00001
>Fatal Error message upon trying to access the secure url (when clicking
>on a "Buy Now" button, for example). I've read in the archives that
>this sometimes indicates a permissions issue, although I have not yet
>been able to determine specifically which permissions need to be
>verified and changed, if any (what files? which directory?)
>
>I'm thinking that this problem may be resulting from the shared SSL
>configuration, but I am not exactly sure where to begin. I've already
>confirmed that our versions of Miva and Empressa do in fact work under
>Windows Server 2003, as we have 2 other Miva stores currently running
>fine on our server (the SSL URLs for these Miva sites have not yet been
>updated to use the shared SSL). So I'm narrowing this down to the
>shared SSL configuration, and am assuming that some vital step may have
>been missed. Could anyone here be so kind as to offer some assistance
>in helping us resolve this matter?
>
>Thank you,
> - [email protected]
>
>*
>*
>
>
>
>
>
--------------010808000608000609020602--
Comment