Guys, I could really use some help.

My webhost has a shared SSL cert, and it seems like everyone else who has tried, I am unable to get this to work with cubecart.

Here is the deal:

My shared SSL certificate explanation from my webhost tells me to create a /ssl directrory on my root. The path to this is https://ssl4.blabla.net/~sc14077-FOOO/ , well, you get my point.

I have my cubeart files uploaded to my server in /tntservice.net/gifts/ which phpinfo() tells me is
/home7/sub002/sc14077-FOOO/www.tntservice.net.

Now, I set up my cubecart with those paths and enabled ssl, and everything works fine until I attempt to go to the admin section, as others have said.

Now, having read a ton of answers, and checked the help topics on SSL, I have come to the conclusion that if I go to the /ssl directory on my root, by using the web address they gave me for my ssl cert. (https://ssl4.blabla.net/~sc14077-FOOO/) it is supposed to redirect me to my root directory, but it doesn't.

There are files in my /ssl directory that are used by other websites I host, and when I click that link, it just shows me a directory of those files.

So, the way I have cubecart set up, it is looking for: https://ssl4.blabla.net/~sc14077-FOOO/admin/index.php and returning a not found because I do not have /ssl/admin/ on the server

What is going on here, and why is it not working as it says on here it should? Did I do something wrong?

Do I have to upload my entire /admin directory to my /ssl/ directory in order to make it work? Doesn't seem to me like that will help any.

Please, if you are good at this kind of thing, let me know how to fix this, I would be forever grateful!

Hi everyone....well, it seems that I join the queue!
I have XTCommerce, osCommerce and ZENCart running on my server. All work fine, shared ssl is no problem. Some other CMS like Joomla and Typo3 run like a charm with shared ssl as well. Now with cubecart: I am lost! I tried all combinations I have found in the cubecart forums, really, everything gives me a loop. I checked via sslcheck.php and it seems that it is ok as well. Where is the hidden secret, guys? Why does it only happen with cubecart? I am ready to buy a real ssl cert, but i read in the forum that it might fail as well?! I have just had many problems with XTCommerce (oscomerce fork) and started the whole migration to cubecart. Now this silly ssl problem eats up my time. I am happy to pay for cubecart, I have another 3 shops waiting to be set up. But I am a bit careful now, if ssl does not work there is no point in buying it. No offence, ok! I don't blame the developers but can't this just work like on other cart/cms systems? Any help very appreciated!

Best regards,
andre

I happily run a shared SSL with NO problems! In fact, mine is a wildcard shared SSL that covers all subdomains as well.

Someone PMed me recently about this, but I couldn't find the link back.

I have an installation within a subdomain. The shared SSL works by operating through all subdomains of the main doman, in other words: *.domainName.com.

Here are the settings I am using for such an instalaltion. I have replaced the specifics with generic names, but you should be able to follow the structure. By the way, the CubeCart Congif Tool is brilliant for fiddling around and repairing such settings:

$config['rootDir_SSL'] : /home/content/B/r/i/HostUserName/html/shop/shopName
$config['rootRel_SSL'] : /
$config['storeURL_SSL'] : https://shopName.domainName.com
$config['ssl'] : 1

This relates to the normal configuration settings being:

$glob['rootDir'] : /home/content/B/r/i/HostUserName/html/shop/shopName
$glob['rootRel'] : /
$glob['storeURL'] : http://shopName.domainName.com

In my installation, the shopName is the same as the subdomain, and it's set up as this:

Physical URL : http://www.domainName.com/shop/shopName
translated URL: http://shopName.domainName.com/

In the above example, the folder /shops can be deleted if the store is installed at the root.

This works for multiple installations I have, which are all set up as subdomains.

If you are using a single domain shared SSL certificate, it won't work for a subdomain, unless your provider has set up the certificate specifically to cover that, however it should work based on the following settings:

$config['rootDir_SSL'] : /home/content/B/r/i/HostUserName/html/shopName
$config['rootRel_SSL'] : /
$config['storeURL_SSL'] : https://www.domainName.com (Your certificate should be exactly as this)
$config['ssl'] : 1


This relates to the normal configuration settings being:

$glob['rootDir'] : /home/content/B/r/i/HostUserName/html/shopName
$glob['rootRel'] : /
$glob['storeURL'] : http://www.domainName.com/

Delete /shopName if you have installed your store at the root.

By the way, I only was able to resolve this originally with the help of the CubeCart technical support (paid), they were able to sort the problem out straight away.

If that's not working, please can you post up your configurations, leaving out passwords. Sometimes, even the most smallest things can cause the biggest problems.

Brivtech: Thank you, this is a great piece of info! I am sure that I tried all this but I will do it again, and i hope that I have overseen something

Thanks again, will keep you updated.

Well, I had a heck of a time getting my shared SSL working. I can give you the settings I used in hopes they will help you. my host never gave me my certificate or put it in a specific location. They just basically told me my root secure url to my store:

https://cp3.hostek.com/~visionkn

This is what I used for my Absolute Store URL

For my root secure path my host gave me:
/~visionkn/store/

I am using 3.0.12 so that's all the info you need. For you my guesses would be:

Absolute Store URL:
https://ssl4.blabla.net/~sc14077-FOOO/store (or replace store with where ever you put your CC)

for Root secure:
~sc14077-FOOD/store/ (or again, replace store with whereever you put your cc install)

This is the only way I was able to get the whole cart working and not lock myself out of my admin, not crash when leaving a ssl page etc.
One valuable piece of info I read in another post is that EVERYTIME you try a new setting for these SSL connections, you need to go into your browser, clear your cache/cookies, close the browser and then open a new one. Otherwise you won't see the fruit of your changes and will make you think the right settings aren't working.