Connection Partially Encrypted
Posted by letnes, 09-16-2008, 11:03 PM I get the Connection Partially Encrypted message when I connect to my website. The site is getting info from two servers. The SSL certificate is installed on one of the servers.. Can I install the same certificate on the second server or do I need to get another cert? Thanks.
Posted by JenLepp, 09-16-2008, 11:25 PM You'll need to get another cert to encrypt that URL.
Posted by lamerfreak, 09-16-2008, 11:46 PM Servers have the same name (part of a cluster)? Or two separate servers, separate names, different domains?
Posted by Tim Greer, 09-17-2008, 01:04 AM You might very well be able to install the same SSL certificate on both servers. It really depends on how it's running (cluster, etc.) It can also depend on the type of certificate. There's no reason to conclude you can't. What exactly are you attempting to do?
Posted by apnicsolutions, 09-17-2008, 05:42 PM If you name your other HTTP servers via subdomains on a single domain, you can also purchase a wildcard certificate that might work out well in terms of limiting additional prices.
Posted by apnicsolutions, 09-17-2008, 05:44 PM Removed post. Last edited by apnicsolutions; 09-17-2008 at 05:45 PM. Reason: Posted in wrong window
Posted by Tim Greer, 09-17-2008, 05:49 PM A wild card certificate could work, but if it's some load balancing solution or something similar, then the same domain can use the same certificate across the two systems and on different IPs. So, it really can depend on several factors, not to mention if both need a certificate for direct access over the web server anyway. I think more information is needed to offer any real suggestions or help to the OP.
Posted by IceDog, 09-18-2008, 12:30 AM Other than your second server... Check your entire source for 'http://'. For instance, Google Adsense doesn't have an ssl connection, so my page cannot be fully secure unless I take off Adsense.
Posted by Tim Greer, 09-18-2008, 12:49 AM Reading the last reply by IceDog, I think I might have misunderstood the original question. If there are security warnings, yes, check for any http:// (non https://) calls for anything. Images, javascript, popups, etc. Any full http:// URL without being secure will warn or error with some browsers, so you need to ensure that you don't call images, embedded files, etc. with the full URL and you should call them with absolute or virtual paths (being /path/here or path/here, rather than http://domain.com/path/here -- though you can always use https://domain.com/path/here for a full URL). I hope that makes sense, assuming that's what the original question pertained to.
Posted by letnes, 09-18-2008, 12:57 AM I need to find out more informatiom on the second server.
Posted by tajidyakub, 09-18-2008, 09:26 AM In most case you should get another cert, as in other condition mentioned above for special case like a wild card server certificate it is true that it will depend on your cert. I only have experience with Thawte SSL, and the wild card webserver certificate they offered only valid in one server, unless you bought an addon.
Posted by lamerfreak, 09-18-2008, 09:36 AM You can copy the private key and cert over and get it working on another server with the same name, but you're usually only doing that in failover/clusters... and generally an authority wants you to buy an extra license on the same cert for that, though I'm not sure how/if they can enforce it. Other than that, really need to know what the setup is to answer more effectively, yeah.
Posted by tajidyakub, 09-18-2008, 09:39 AM This I just know, Thanks for the info, will give it a try some time.