GoDaddy SSL Not Working

Hmm, nope, not strange since it's quite a good marketing strategy. Just funny it's so obvious.

http://www.loudsign.com/ <-- they're using that domain name for a quote thought its actually theirs (stole layout, almost the same pricing)

"Go Daddy's reseller program has been a great way for us to break into the domain name registration business and make extra income without all the usual headaches and risks associated with starting a business...."
- Garry McGillivary, www.loudsign.com

Maybe one could make a sport of finding all of their "sister companys"
 
GoDaddy, WildWest and Starfield are really the same company.

loudsign.com is a reseller. All WildWest resellers look almost exactly the same.

jaapvstr, I don't see what you mean about the pricing.

If you want to find a whole bunch of WildWest resellers, run this Google search and look around the sites Google returns ;) .

And then decide if you want to become a GoDaddy reseller.

Instead of WildWest, I've always thought they should call themselves "WildZoo".

Hey, wildzoodomains.com is available :D

Jeff
 
i not see any solutions for this problem ??
i also have goDaddy ssl cert, but when i use firefox, it show me test page. but when i use ie, it show my site.
how to solve it ??
 
The only way I can see your problem happening is if you have a bad cache in your FireFox browser. What site has the problem?

Jeff
 
How to make it work (at least how I got it to work)

It seems every time I get a new SSL or renew an SSL certificate for a client I go through the same problems with DA and GoDaddy. I finally figured it out and have precise steps on how to do it again. Hopefully by sharing it with the world I can save others problems and myself later by having an offsite hard copy of the instructions somewhere...

1. Get your SSL Cert from GD.
2. Paste the contents of yourdomain.com.crt BELOW the RSA PRIVATE KEY (that should automatically be there) on the page https://yourdadomain.com:2222/CMD_SSL?DOMAIN=yourdomain.com.
3. Make sure you have the radio box "Paste a pre-generated certificate and key" selected.
4. Hit Save at the bottom.
5. After saving, it should say "Certificate and key files saved" or something like that. Then click on the "Click here" part of "Click Here to paste a CA Root Certificate".
6. Here's the tricky part. What you need to paste in this box is a combination of the file gd_intermediate_bundle.crt and gd-class2-root.crt. Not sure if the order matters, but I do it in the order listed above. You end up having 4 -----BEGIN CERTIFICATE-----/-----END CERTIFICATE-----. I will paste the 4 of them with the first and last lines of each certificate so you can double check to make sure you have the right ones.
7. Hit save.
8. Do NOT manually restart Apache from CLI or Service Monitor. I'm not sure why, but it seemed whenever I restarted/reloaded Apache manually it wouldn't work, but when I let DA do its thing, it did. I don't know if anything is happening in the background, maybe I'm just on drugs, but I know I tried these steps before but manually restarted Apache without any success.

Here's what it should look like:

-----BEGIN CERTIFICATE-----
MIIE3jCCA8agAwIBAgICAwEwDQYJKoZIhvcNAQEFBQAwYzELMAkGA1UEBhMCVVMx
...
U+4=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIE+zCCBGSgAwIBAgICAQ0wDQYJKoZIhvcNAQEFBQAwgbsxJDAiBgNVBAcTG1Zh
...
SxOaFIqII6hR8INMqzW/Rn453HWkrugp++85j09VZw==
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIC5zCCAlACAQEwDQYJKoZIhvcNAQEFBQAwgbsxJDAiBgNVBAcTG1ZhbGlDZXJ0
...
W/POuZ6lcg5Ktz885hZo+L7tdEy8W9ViH0Pd
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIEADCCAuigAwIBAgIBADANBgkqhkiG9w0BAQUFADBjMQswCQYDVQQGEwJVUzEh
...
ReYNnyicsbkqWletNw+vHX/bvZ8=
-----END CERTIFICATE-----

Hopefully that helps people. For whatever reason just using gd_intermediate_bundle.crt didn't work for me, and this did...

-Percy
 
Thanks for the write-up. I was just moving a site from Plesk to DA today and had to re-install the SSL certificate and forgot the steps needed to complete the chain for the basic Godaddy TurboSSL.

I remember googling a bunch when first installing the TurboSSL and finding out the need to combine the root and intermediate bundle was a common issue for a lot of people since it was a step that wasn't described in Godaddy's help section.
 
got a question, in the SSL setup, where you enable/disable it, it says this
private_html setup for mydomain.com - (SSL must be enabled above)
Use a directory named private_html
Use a symbolic link from private_html to public_html - allows for same data in http and https
Click to expand...
is one better than the other?
if I check the symbolic tic box the next screen tells me that all data in the private_html folder will be deleted..
Also what does this mean exactly
Secure SSL (Ignored if not allowed)
Click to expand...
thanks
 
RE: private_html vs public_html

If you have a web application like osCommerce all the files are in public_html, and the app controls the SSL function. I had to create a sym-link from private_html to public_html so the SSL functions would work. With the symbolic link, the server will look for everything in the public_html dir.

If it's easy for you to break your application up into two directories, then private_ should be fine....but for me it would require two full duplicate copies.

I'm fairly certain there's no significant security difference, but I'd love to hear about it if there is. :confused:
 
The security difference is that with everything in public_html your visitor can call up any page with http (insecurely) instead of https (securely), and so expose data across the 'net which shouldn't be so exposed.

So we prefer using private_html for secure pages.

Jeff
 
netstepinc said:
If you have a web application like osCommerce all the files are in public_html, and the app controls the SSL function. I had to create a sym-link from private_html to public_html so the SSL functions would work. With the symbolic link, the server will look for everything in the public_html dir.

If it's easy for you to break your application up into two directories, then private_ should be fine....but for me it would require two full duplicate copies.

I'm fairly certain there's no significant security difference, but I'd love to hear about it if there is. :confused:
Click to expand...

Thank you
I did just that for the symbolic link, pages such as admin, checkout, and accout creation are https, so all looks good. Just had to change the config file to reflect the ssl.....

PS

I followed Percy's scheme, only diff was that I didnt get a gd-class2-root.crt, but all seems to be working well as per his instructions, I just left out the part adding that cert
 
jlasman said:
The security difference is that with everything in public_html your visitor can call up any page with http (insecurely) instead of https (securely), and so expose data across the 'net which shouldn't be so exposed.

So we prefer using private_html for secure pages.

Jeff
Click to expand...

So Jeff, guess its not a good thing LOL,, now like I said anytime you visit a page like checkout, it goes to https, its just product pages that stay http, Should we move all files to the private folder?
Another thing I found, after committing to the symbolic link, the private folder is deleted, on a test site I re created the private folder, went back to DA and changed to using a private_html folder but there was an error with "forbidden" showing on browser..
does this mean that there is no going back once you have done the symbolic choice?
 
hi all my first post here
i have same problem with godaddy ssl certificate

i install certificate pasted my key and godaddy certificate in directadmin panel

then i pasted the intermediate certificate in "click here to paste a ca certificate"

now the certificate work with ie but not with firefox

my site is https://www.pixael.com

can you help me?
 
AndyII said:
So Jeff, guess its not a good thing LOL,, now like I said anytime you visit a page like checkout, it goes to https, its just product pages that stay http, Should we move all files to the private folder?
Click to expand...
That's really up to you. Secure http puts a much greater load on your server for several reasons:

encrypting/decrypting takes both time and server resources

and

your browser doesn't store any files sent as encrypted so everything (including images) used in the encrypted folder has to be sent each time, encrypted and decrypted (yes, even the images) each time.

So we only use encryption for the minimum amount of information which we feel needs to be secure.

But that's sometimes a lot. For example http://domains.nobaloney.net switches to encryption for everything.

(Don't buy domain registrations there; it's high priced :) ).
Another thing I found, after committing to the symbolic link, the private folder is deleted, on a test site I re created the private folder, went back to DA and changed to using a private_html folder but there was an error with "forbidden" showing on browser..
does this mean that there is no going back once you have done the symbolic choice?
Click to expand...
I've never tried it. Did you actually create the folder manually before switching back? If so, have you tried going back without recreating the folder, letting DirectAdmin recreate it?

Jeff
 
When I look at the SSL information in Firefox I see that the intermediate Certificate isn't installed. Try installing it again.

Jeff
 
Obviously Certificates without Intermediate (root) Certificates are easier to install, but only by about two clicks. Most important to buy a Certificate that comes with a full warranty, and from folk who know how to support installation on DirectAdmin.

Or buy a Cert that comes complete with Installation.

I used to have a thread advertising our Certificates but someone complained to me, so I removed it.

I'll soon be doing a webpage for our Certificates supported fully in DirectAdmin and with optional DirectAdmin installs; then perhaps I'll link to it in my sigline or as an answer to this sort of question :) .

Jeff
 
symbolic links?

Maybe I'm totally missing this but how exactly do I create a symbolic link so private_html points to public_html?

Thanks
Ryan
 
rkoechel said:
Maybe I'm totally missing this but how exactly do I create a symbolic link so private_html points to public_html?
Click to expand...

Click "Domain Setup" for the account in question, click the domain name, then choose "Use a symbolic link from private_html to public_html - allows for same data in http and https".
 
rtaylor said:
Click "Domain Setup" for the account in question, click the domain name, then choose "Use a symbolic link from private_html to public_html - allows for same data in http and https".
Click to expand...

Where is this in DirectAdmin? Is it at the admin, reseller or user level? I cannot see it.

Thanks.
 
You must log in or register to reply here.
Back
Top