Timeline for SSL certificate on https://secure.domainname.com
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2013 at 19:55 | comment | added | Ian Young | Glad you got it sorted. Don't let the hosts fob you off with a subdomain unless you specify you want it. It is always an option to get a wildcard SSL certificate which would apply to any subdomain too but that will be more expensive. | |
| Mar 27, 2013 at 17:15 | vote | accept | Lloyd Hill | ||
| Mar 27, 2013 at 12:54 | comment | added | Ian Young | I'm confused. Why have you made mention of secure.domainname.com if that doesn't exist? | |
| Mar 27, 2013 at 10:22 | comment | added | Lloyd Hill | No, the SSL is installed to the www directory, which is also where EE is installed. There is no subdomain called 'secure'. The SSL certificate will only work for files in the www folder (root domain). | |
| Mar 27, 2013 at 10:06 | comment | added | Ian Young | That will be the problem then. SSL certificates are specific in that they're applied to an exact domain or subdomain. Your host may have misunderstood what you wanted and applied it to a new subdomain. So unless you have EE installed on that subdomain you wont be able to make a secure connection. Even if you setup a redirect in your .htaccess file it still wouldn't be connecting securely and would throw warnings. You either need to tell your host to configure the SSL certifcate on your root domain or install EE on secure.domainname.com. | |
| Mar 27, 2013 at 8:21 | history | answered | Ian Young | CC BY-SA 3.0 |