SSL help

**RFH Reseller: penfold33** · 20th July 2011, 12:37 PM

Hi

I've got a domain which I need to apply an SSL certificate to. I've done it once before but it was a while ago so wonder if I'm missing something:
I've paid the 'One Time setup fee' in Helm, applied it to the domain and created a test self signed certificate and applied that to the domain. But when I go the domain with the secure start (https://www.domain.co.uk) I just get "HTTP Error 403.14 - Forbidden: Directory listing denied".

Am I right in thinking the files don't need to go anywhere special? That all content in the wwwroot directory should also be available under https? That's how my other domain looks.

I've just checked on Nominet and, unlike the other domain which has RFH nameservers, it looks like the nameservers for this domain aren't pointing to RFH. The client must be just pointing the web to me. Can anyone help with what changes I need to ask the client for, so the https addresses work? Do they need to setup/change a nameserver record?

Thanks

Jane

**RFH Reseller: SKILLIT** · 23rd July 2011, 07:52 AM

I don't think that the client is just pointing the web to you or the https would not give that response code. Possibly it is redirecting or serving in a frame.
What does the host www resolve to? that would confirm if it points to your host or not.
You could also have a look at the html / response codes of a http request in a browser using the developer tools.

**RFH Reseller: penfold33** · 26th July 2011, 10:34 AM

Hi Skillit

Thanks. The normal http works fine and the website shows up. Just not when I use https instead. I'll get the client to contact the host and see what they say. Just wanted to make sure I hadn't missed anything obvious in the installation of the ssl cert first.

Thanks

Jane

**RFH Reseller: SKILLIT** · 26th July 2011, 11:13 AM

One quick double check would be to repeat the https and look in your server logs - That would prove that the https is not getting to you.

**RFH Reseller: penfold33** · 31st August 2011, 09:08 AM

Hi

I found an old thread from someone who had a similar problem and I think it's because the IP address is changed when the certificate is installed. As I don't control the DNS (the domain is hosted by the client's hosts), I assume I need to get their hosts, to change the IP address? I've looked in the DNS zone editor for the domain and I've got an '@' record and a 'www' record pointing to 89.238.132.54 and a '*' record pointing to 89.238.132.13.

Am I right in thinking that I need to get the hosts to change from 89.238.132.13 to 89.238.132.54, and that both http and https will then work?

Many thanks

Jane

**RFH Reseller: SKILLIT** · 31st August 2011, 11:38 AM

I think you are on the right track - In helm if you look at the Web Site Settings you will see the Dedicated SSL IP. I think that should work for both.