Hi,

I think I have been a bit stupid here. Can anybody help?

My business website is http://thelogocompany.net

I wanted to enable the lock for my orderform at http://thelogocompany.net/orderform.htm so I got a freeSSL cert for http://thelogocompany.net and had Mchost install it at https://thelogocompany.net

Now...All I see at http://thelogocompany.net is a DOT...just one small dot...no website!

I was under the impression that I could still use http://thelogocompany.net and just point my orderform to https://thelogocompany.net/orderform.htm

Did I screw up here?

Please explain

Thanks
Simon

No there is no reason that would have screwed up your site. Contact Mchost and get them to investigate and fix the problem for you.

Nope, it should work regardless of which page it points to under your public_html directory.

Open a ticket and let Marc or one of his staff look into this for you.

[edited] Just to note, You don't think when they installed the cert, that they setup the domain as "https" instead of "http" do you?

Never tried that on purpose, so I don't know what effect it would have on the rest of your site.

While waiting to hear from support though, check the files on your site, and make sure you have only 1 index page.

something is wrong with the apache configuration :)

Hi,

Thanks for the replies so far. I have put a ticket in to Mchost already...and posted this on their forum. I fear my site will now be down for days at it took 2 days to install the cert.

Is my initial understanding of how this should work ...sound...or have I missed the point somewhere. ie...should I still be able to use http://thelogocompany.net or do I now always need to use https://thelogocompany.net for all my pages?

Simon

You should be able to use https or http.

Originally posted by SimonMc
Hi,

Thanks for the replies so far. I have put a ticket in to Mchost already...and posted this on their forum. I fear my site will now be down for days at it took 2 days to install the cert.

Is my initial understanding of how this should work ...sound...or have I missed the point somewhere. ie...should I still be able to use http://thelogocompany.net or do I now always need to use https://thelogocompany.net for all my pages?

Simon

Yikes... 2 days to install a cert? OH MY :eek:

To answer your last question, nope! only call https://thelogocompany.net on any page/s you want to collect important data on.

FreeSSL rocks with that telephony authorization system they have in place! ;)

if you have cpanel... installing ssl would be just a few clicks :)

Originally posted by inteltechs
if you have cpanel... installing ssl would be just a few clicks :) Where is this available in Cpanel? :(

Do you mean WHM?

Originally posted by inteltechs
if you have cpanel... installing ssl would be just a few clicks :)

I do have cpanel but I believe you need root access to the server to install a certificate...or a dedicated IP address....not really sure how it is done but at McHost they install the certs for you.

Could this be a problem.....When I ordered the certificate it said what domain do you want it for and I said.....http://thelogocompany.net And then McHost asked me if I wanted it installed on x y or z where x = https://thelogocompany.net so I said yes to this. Then I got a support answer sayning it had been installed on https://123.123.123.123 (ficticious IP) So....here I am

Ordered cert for http://thelogocompany.net
Had it installed on https://thelogocompany.net
Get a response saying installed on https://123.123.123.123

Does this sound correct to people or has their been a misunderstanding on my part somewhere along the way?

Thanks again.

Simon

yeah you need root to install ssl or if you have a reseller account with ssl control, you can install it yourself :)

installing ssl with cpanel is copying and pasting :) it won't take 2 mins :)

Originally posted by SimonMc


Ordered cert for http://thelogocompany.net
Had it installed on https://thelogocompany.net
Get a response saying installed on https://123.123.123.123

Does this sound correct to people or has their been a misunderstanding on my part somewhere along the way?



Anyone?

Simon

Personally I always use www.domainname.com for the common name on certs.

When I install said cert, I install them on www.domainname.com, which works flawlessly.

Like I said earlier, I do feel that is the problem in your case. The cert was ordered for http, yet installed for the domain https.

You can quote me on that, but if it's wrong... I will deny it from here out! :stickout: ;) j/k Simon

I wouldn't deny steering you wrong if it is.

Originally posted by shoney
Personally I always use www.domainname.com for the common name on certs.

When I install said cert, I install them on www.domainname.com, which works flawlessly.

Like I said earlier, I do feel that is the problem in your case. The cert was ordered for http, yet installed for the domain https.

You can quote me on that, but if it's wrong... I will deny it from here out! :stickout: ;) j/k Simon

I wouldn't deny steering you wrong if it is.

Surely http and https are not domains?

Simon

By the way..I heared back from McHost...So thumbs up to that! They said that they had to reload the DNS because the IP address has changed and I am now waiting for it to view depending on how quickly my isp refreshes the cache.

So...can anyone see my site? or is it just a sad little dot...like it is for me :crap:

Simon

Originally posted by SimonMc
Surely http and https are not domains?

Simon

Simon

Of course they aren't domains, Simon! gesssssh

But you didn't have a http[secure] domainanything.com as of yet. That was my point

I can get to your sight, but it is really slow, really slow.

Yes...I think McHost are having some secret problems that they are not mentioning!

Simon