cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution
Highlighted

How to install a SSL on a subdomain

Hi ,

can anyone help me with installing a SSL on a subdomain bought from Go-Daddy.  I tried installing the certificate that is installed on my primary domain but it returns an error.  

My subdomain is redirecting to a .net application that's running on a local server which is natted with a public IP address.  Will I be able to run this application on https ?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Resolver III
Solution

Re: How to install a SSL on a subdomain

Hi, 

 

If you have a web server with HTTPS, you can certainly use it as a proxy for insecure (http only) internal services.

 

The first thing to check is that your certificate covers your new subdomain as well - you either have to add it to your existing certificate (probably easiest), get so called "wildcard" certificate, or get a separate certificate just for the new subdomain. You need a separate section in your webserver configuration so you can set a different path to the second certificate. 

 

In terms of getting it up and running - you can start with sub-path rather than subdomain, I would change your net.mydomain.com to mydomain.com/net in your configuration to make sure the end-to-end flow works. Once you get a new certificate your can finalize the setup with your new subdomain.

 

Dan

 

———

I've worked around (not only) SSL security for over 20 years in enterprises and startups. 

I am now running an HTTPS expiry management service KeyChest.net

View solution in original post

1 REPLY 1
Highlighted
Resolver III
Solution

Re: How to install a SSL on a subdomain

Hi, 

 

If you have a web server with HTTPS, you can certainly use it as a proxy for insecure (http only) internal services.

 

The first thing to check is that your certificate covers your new subdomain as well - you either have to add it to your existing certificate (probably easiest), get so called "wildcard" certificate, or get a separate certificate just for the new subdomain. You need a separate section in your webserver configuration so you can set a different path to the second certificate. 

 

In terms of getting it up and running - you can start with sub-path rather than subdomain, I would change your net.mydomain.com to mydomain.com/net in your configuration to make sure the end-to-end flow works. Once you get a new certificate your can finalize the setup with your new subdomain.

 

Dan

 

———

I've worked around (not only) SSL security for over 20 years in enterprises and startups. 

I am now running an HTTPS expiry management service KeyChest.net

View solution in original post