|
#1
|
||||
|
||||
|
I'll start by saying that HG's shared SSL feature was a strong selling point for me. But the Cert warning just won't fly. Very disappointing. So now I'll be purchasing my first SSL cert. Looking for advice...
Registerfly.com is selling a "starter SSL" for $24.99. It seems to be nearly identical to thier $99 Geotrust cert, but without the recognized brand name. Knowing that Hostgator charges $50 to install any 3rd party cert, I've had the attitude that an extra $25 is worth it to keep the eggs in one basket and go with the HG $100 package. This way, if there's a problem I won't have two companies each claiming the other is at fault. Anyone have any opinions on this issue? I'd like to get it right the first time. |
|
#2
|
|||
|
|||
|
Quote:
Tracy Smith webhost@wichitasgateway.com
__________________
WichitasGateway.com the gateway to the Wichitas Gateway to the web |
|
#3
|
||||
|
||||
|
That is an excellent solution. Thanks!
Question: How does this appear in the address bar when a secure page is accessed? Your domain?... Your IP + /username?... |
|
#4
|
||||
|
||||
|
Quote:
Thanks, Ben
__________________
Gators love marshmallows. |
|
#5
|
||||
|
||||
|
Why don't you just let HostGator install their comodo certificate for you? It costs $75 and includes installation. I had them do it 2 days ago and it works great! One thing: make sure you specify either www.yourdomain.com or just yourdomain.com. Whichever you choose, your secure URL link should reflect the same or you will get an ssl warning message.
Out of curiosity, why doesn't HG allow SSL installation via WHM? |
|
#6
|
||||
|
||||
|
Okay, HGs Comodo SSL has been installed on my main account and I intend to share it. Could use a little direction before I start building....
I believe Tracy's solution involves putting all the clients secure pages, shopping cart checkouts, or what have you- in a sub under my own reseller domain. Like this? https://clientsdomain.mydomain.com/securepage.html That makes sense. But I'm not following Ben. Does this also involve placing stuff in a sub, or is there some passthrough process that I should know about? I tried https://mydomain.com/~clientsusername/securepage.htm - no go. Did I miss something or is a subdomain the only way to share the SSL? Thanks for the helps!
|
|
#7
|
||||
|
||||
|
Thomas,
Quote:
Stef. |
|
#8
|
||||
|
||||
|
Quote:
Last edited by Thomas; 09-11-2004 at 09:25 AM. Reason: mistaken result |
|
#9
|
||||
|
||||
|
Quote:
This could be f.e. if you have an image on that page that is defined as an URL instead of a relative link. If the URL goes to http://... it is indeed a link to a non-secure page. You could also have f.e. a header or footer included in your page that contains links to a non-secure page. Can you check that? Stef. |
|
#10
|
||||
|
||||
|
Quote:
|
|
#11
|
|||
|
|||
|
Quote:
but the same result as Thomas. Goes to my 404 page instead of the clientpage.htm with secure status of my SSL. |
|
#12
|
|||
|
|||
|
Quote:
|
|
#13
|
||||
|
||||
|
Thomas, I am forwarding this thread to Ben who should be able to provide further support. I will keep an eye on it to make sure it is not forgotten.
-Justin |
|
#14
|
||||
|
||||
|
Quote:
For the record, I've gone ahead and set things up similar to what Tracy described at the beginning of the post. I made a sub on my own account that uses the clients domain name (minus the dot com), and placed the clients secure pages/scripts there. Access is like this: https://mydomain.com/clientsname/securepage.htm Fortunately the client is cool with having my domain name in the mix - the cost savings also helps to convince. Otherwise, sharing the SSL would be out of the question. Honestly, if he had to choose between this URL and https://mydomain.com/~clientsusername I think he would choose what he has now. Having his own domain name in there means a lot.I should also mention that this guy, like most of my clients, is completely hands off. They don't even want to see a cPanel, much less an FTP app. Thanks for all the input everyone! Last edited by Thomas; 09-16-2004 at 02:13 PM. Reason: description |
|
#15
|
|||
|
|||
|
Just to clarify, the original post says $50 to install thrid party cert, or $100 to acquire and install from HG directly, and another post indicated that it's only $30 to install third party cert, and only $75 to acquire and install directly from HG.
I've found the latter to be what is displayed on HG's site, were those prices lowered since the original poster inquired about previously, or is there some other reason these numbers are different? Also, the charge for the cert itself, is that a one-time fee, or is it per year? I've seen it sold elsewhere per year, but HG's site does not specify... Thanks, Karsten |
|
#16
|
||||
|
||||
|
Karsten,
we sell Comodo 128 bit certificates for $75 and this includes the installation. This is for one year. If you already have a certificate that needs to be installed there's a $25 installation fee. Stef. |
|
#17
|
||||
|
||||
|
Quote:
HG - FYI: If you go here- http://www.hostgator.com/resellers.shtml -and click on the ? next to Private SSL, it still says $30 installation. |
|
#18
|
||||
|
||||
|
Thomas,
Quote:
Stef. |
|
#19
|
||||
|
||||
|
Quote:
I have never purchased/setup an SSL certificate before, so could you help explain exactly which Comodo product HG sells and installs for you? For instance the site seal at http://www.hostgator.com/ssl.shtml doesn't look anything like the site seals on http://www.trustlogo.com (run by Comodo). I'm also trying to figure out if it is the InstantSSL or InstantSSL Pro offered at http://www.instantssl.com/ssl-certif...ica&country=US (also run by Comodo). I am thinking it's probably the standard InstantSSL, but it says the site seal is not included with that type of certificate. Just kind of confusing. Thanks... David |
|
#20
|
||||
|
||||
|
David,
as you can see on the site you mentioned there are different types of certificates like InstantSSL, InstantSSL Pro, etc. You are correct that HG offers InstantSSL. This does not include a free TrustLogo (as is with eg. Pro). The logo you can put on your site and can find at http://www.hostgator.com/ssl.shtml is the Comodo InstantSSL Secure Site seal. You can also find it in their site's support section Hope this clears things up a bit, Stef. |
|
#21
|
||||
|
||||
|
Quote:
Thanks for the info. Yes, I do see that site seal on their support section. Let me know if I have this straight now. The free seal that you can display with an InstantSSL certificate (sold by HG) basically validates that your site is SSL secured for financial transactions. The various Trust site seals provide realtime website identity validation (a perceived "touchy feely" for customers) in addition to the SSL secure validation in some cases. I saw one that said "SSL Secure & Authentic Site", another that was just "Authentic Site", one for "Authorized to Accept Credit Cards", and one for Partner sites. If I'm correct so far, the only thing that still has me confused is the difference between the "SSL Secure & Authentic" and "Authorized to Accept Credit Cards" since they sound like basically the same thing to me. Another appearent overlap is with the standard HG provided SSL seal and those two as well. I guess I should just think of it as the HG seal is the base level SSL authentication, and the Trust Logos are the premium level??? Thanks for your help. David |
|
#22
|
||||
|
||||
|
David,
that's correct. The TrustLogo delivers your credentials in realtime from the IdAuthority to your customers when they hover over it with their mouse (point to verify). It's only available with the Pro and Premium certificates. So you could indeed see the Secure Seal (for InstantSSL) and the TrustLogo's as a distinction between the different types of certs. Remember thought there's no difference in 'SSL quality' between the certs! I have no experience with the TrustLogo's myself. Maybe you can ask them what exactly is the difference between the logo's. There should be no difference in the validation procedure to achieve the "SSL Secure & Authentic" and "Authorized to Accept Credit Cards" logo's. Maybe it's just a point of sale... Customers may be more comfortable seeing the 'Credit Cards' logo next to the 'SSL Secure' logo when they actually want to buy something... Stef. |
|
#23
|
||||
|
||||
|
Thanks Stef. That makes sense. I just wanted to make sure I was not missing something here in regards to the perceived differences in levels of authentication. Since I am curious, I'm going to inquire with them and see what they say. Will post back here if I get back any useful information.
David |
![]() |
| Bookmarks |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Some Quick Questions | Anonymous | Pre-Sales Questions | 8 | 07-29-2004 02:15 AM |
| refugee has tons o questions | freelancing | Pre-Sales Questions | 1 | 06-29-2004 01:16 AM |
| A few questions I'd like to ask. | vandora | Pre-Sales Questions | 1 | 06-04-2004 04:43 AM |
| Reseller Questions. | ketamine | Pre-Sales Questions | 3 | 01-30-2004 10:21 AM |
All times are GMT -5. The time now is 04:01 PM.





Otherwise, sharing the SSL would be out of the question. Honestly, if he had to choose between this URL and 




