Jump to content
  • Checkout
  • Login
  • Get in touch


The e-commerce.

Own (not shared) SSL on different IP problem


Recommended Posts



I have my own SSL cert on https://secure.mysite.com (an IP based site)


I also have http://mysite.com (a differnt IP based site)


They are both on the same server. Other than that they are not linked, shared or pointed to each other in any way.


I have installed this shopping script on http://mysite.com only - and of course it does not work because the script appears to be designed for shared SSL facilities, where one places all files on the one site.


I'm not happy to, but can, duplicate everything so the SSL site mirrors the main site. But will this work? Surely the cookies will get confused! More to the point, the MySQL server will probably spit the dummy!


Is there a viable solution soon (or anytime on the horizon), or is this script meant to be for small personal websites with shared SSLs?


If there is no solution, can anyone recommend a similar script that has already overcome this problem.


Appreciate any input on this.




PS. Yes I have read previous threads. No my SSL is not shared. No I can't ask my hosting company as I don't have one - I rent my own box. No I don't want to get a hosting company and share an SSL. B)

Link to comment
Share on other sites

As far as I know, there are only 2 types of SSL certificates that will work with OSCommerce, or ANY cart for that matter.


1.) A shared SSL on the same server with different IPs, and a different URL. Generally offered for free by Hosts.


2.) Your own SSL, which requires a static IP, and is installed on the same domain as your regular site.


I've never heard of the type of SSL you have, and honestly, I don't see how it would be useful.


NOTE: As of Oct 2006, I'm not as active in this forum as I used to be, but I still work with osC quite a bit.

If you have a question about any of my posts here, your best bet is to contact me though either Email or PM in my profile, and I'll be happy to help.

Link to comment
Share on other sites

Normal Web traffic goes to port 80 on a web server.


When traffic goes to a SSL port (443) it usually checks to see if the certificate is available and/or valid. If everything checks out on the server side, it then serves the exact same pages from the port 80 side but throught the SSL port (443) instead. You get to then see the little LOCK.


This is *IF* you have the SSL and non-SSL on the same server.


If you try to go to ANY site via the https:// designator, you should get either an error that the "The page cannot be displayed" or an error that the site has a certificate but its not assigned to the domain that you are going to.


Usually the latter happens when you go to a hosting server that has various domains on it and one of them has a certificate. Although, it does sound like a bleed over problem of some sort. I know this happens on a Windows box (NT), I've yet to see that happen with a Linux Box. But anything is possible.



I own my own servers and I want to have only 1 server be the SSL server for various domains. I can do this by creating a subdirectory off the main SSL certified domain.



https://stores.mystoreserver.com/store2 etc.


All of the non-ssl pages (regualr port 80) are hosted off onto a compeltely different machine.


I've experienced some really interesting errors and I think its based upon how SSL works when callign it from a different server.


Now its quite possible that someone might have figured out how to do pass through and allow the SSL site to call the non-SSL site for graphicsa nd pages, but that usually leads towards the infamous "secure vs non-secure" pop up.


I'd really be interested to see if anyone has solved this and if so their configuration.


Again, not 2 different IPs on the same server, but 2 totally different servers (SSL and NON-SSL)









Motto for today:

I went to school to become a wit. But I only made it half way.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...