SSL being a right nightmare!!!!

Agggghh, my head hurts.

Ive been building a webshop for my work for a while now and the final step i need to take with it is the SSL. However im having a right nightmare with it.

I wanted to have the secured server at the domain http://secure.martinbrownpaints.net

And the normal catalouge is at
http://martinbrownpaints.net/shop

A few weeks ago i got a trial comodo cert and went to install through cpanel. I made a sub domain for the secured side - secure.martinbrownpaints.net and then sorted the dns out and installed the cert through cpanel. However, it didnt work. I had a look through httpd.conf and cpanel hadent written the relevant data to it for the ssl to work. So i did a little work around creating a new virtual host for it. Bear in mind the whole site was running of its own ip addy at the time. This cured the problem. I set the configure.php files to have the https at https://martinbrownpaints.net/~mbpaints and it worked. I was however concerned about doing the patch in httpd.conf as i assumed cpanel would do this for me.

I contacted my data center and they told me that this was a bad idea as i may break my apache config. And that the ip addresses had conflicts. I was told to delete the sub domain and then create a new acount for the sub domain through whm and then set that to the spare ip and have the standard site running off the other ip. This seams strange to me, but ive gone ahead and done all these changes.

Ive bought a cert and installed it on the secure.martinbrownpaints.net acount and then put the catalouge in the root dir. I then changed the configure.php files to https://martinbrownpaints.net/~mbsecure (This is the new username)

And now it doesnt work at all. See what i mean and click login - https://www.martinbrownpaints.net/shop

I really do not have a clue about what is wrong with the config. Any help would be really appricieated!!!!!

Do you really want your catalog to be run in the secure environment?

The settings in the configure.php files will switch to the secure environ upon payment and this is normally what is done.

You have most likely not set all the url pointers in the configure.php when you moved the catalog files and it is now having trouble finding the files and looking for them at http://martinbrownpaints.net/shop

Search your files for the term "/shop" and see if this might be one of your problems.

kobra:

Do you really want your catalog to be run in the secure environment?

The settings in the configure.php files will switch to the secure environ upon payment and this is normally what is done.

You have most likely not set all the url pointers in the configure.php when you moved the catalog files and it is now having trouble finding the files and looking for them at http://martinbrownpaints.net/shop

Search your files for the term "/shop" and see if this might be one of your problems.

Thats what im trying to do. Enable SSL checkout, which also switches to ssl for logins. I tried what you said but still have the same problem? Can you suggest anything else?

Thanks for the help. :)

Might be advisable to have your hosting company take care of it ... they're the ones with the knowledge of how their system is set up ... and generally should have the skills to do this for you.

You don't want your secured content being served from a different server or account or file structure other than your non-secured content. It should all point to the same place.

Manged to get this sorted now so i thought id post up how i did it for others reference.

I decided to throw away what my data center had said and deleted the spperate acount for the secure subdomain. Then i created the new subdomain on the main domains cpanel and set up the redirection. I then went and sorted out the dns, and put the whole site on a sepperate ip.

Then i went into the shell and went back to my manually patched version of httpd.conf to add in the sub domain and SSL details and restarted apache.

After this i found that the site worked and the subdomain worked on SSL, but it came with an error prompt saying that the cert was not issued by a valid company. Looking through a few sites i found out that this is a comon problem with WHM and intermediate certs, and all i needed to know was this -

Many cPanel versions won't allow proper installation of intermediate certificates via the WHM. That's why we recommend that you use the following manual installation method. This method works 100% of the time with WHM/cPanel.
To complete the installation, you will need the sslbundle.crt file from the ZIP file that was e-mailed to you when your certificate was issued. If you have misplaced it, don't worry - you can download it below:

Download the XRamp intermediates here.

Save the sslbundle.crt file to a directory on your server, and be sure to note the directory path. Generally, you can find Apache's configuration file in /etc/httpd/conf/httpd.conf, but you may need to search for it. Sometimes the SSL configurations are in a file called ssl.conf.

Open the configuration file in a text editor and search for the virtual host. You can search by your server's address or IP address. Once you find the virtual host which matches your host, look for two lines that start with SSLCertificateFile and SSLCertificateKeyFile. Add (or adjust) a line right below those two that should read:

SSLCACertificateFile /path/sslbundle.crt

Save and close the configuration file.

After an apache restart it works perfectly.

Hope this helps anyone who has similar issues....