How long should it take for my SSL certificate to be activated?

[Splinter]

I have economy hosting for my site here at Godaddy and I bought the SSL here, with the certificate being issued yesterday afternoon. I did all this through the chat system with a Godaddy rep and was assured that there was nothing left to do.

No pending actions are showing, it just shows a yellow dot with 'certificate issued', so I'm wondering when my https will go live.

Many thanks.

[CanerGS]

I have same issue actually. 

I have installed my SSL almost 2 days ago and I am still waiting for it.

Does somebody have any idea ?

[Splinter]

I have to assume that Godaddy don't work on weekends and clearly Monday is a holiday. 

Anyway, although my cPanel optimistically said something like 'You're SSL certification will be live in five minutes', I wasn't expecting it to take this long.

I'll be on their chat system on Tuesday, especially since they were so darned quick to take my money and I mean, very quick.

[Splinter]

I'm getting this

[Splinter]

UPDATE

Whilst chatting with an agent on Friday (online chat), I specifically asked if there was anything else that I needed to do for the SSL activation and they said NO.

In fact I needed to modify the .htaccess file for redirection to https with the following code and upload to the root (as specified in the Godaddy help page on SSL:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

I uploaded this file to the root (public_html) about half an hour ago and am now told that it will take another 48-72 hours to take effect, having just wasted four days by NOT uploading the .htaccess file in the first place.

Not what I would call great customer service.

[Splinter · Accepted solution]

Fixed!

Sorry for the double posting. I thought I'd share how I finally fixed this.

I phoned Godaddy support who fixed the mismatch in the backend (identified by whynopadlock.com) and I then re-uploaded the .htaccess file, ran the site through whynopadlock,com again which pulled up a couple of images, which I fixed by amending the URLs in the backend of my forum for those two images, adding an s to the http.

Now my site is secure.