Setting Up https:// Step By Step

Namesilo referred me to ‘Let’s Encrypt’, but I can’t find any step-by-step instructions for automated creation of an SSL certificate. Namesilo’s instructions were of no help (i.e. the onsite instructions). Does an automated process exist and can anyone point me to the instructions?

I am fairly au fait with technical stuff, but this process is new to me and I’m somewhat defeated by the unfamiliar jargon that I’ve come across.

I’m getting ‘too many redirects’ errors when I use the ‘http://’ prefix on my site and when I place ‘https://’ in front of my domain, I get the scary Google notice warning about my dangerous site. So I really need help with getting an SSL certificate installed. Any help will be greatly appreciated.

Please fill out the fields below so we can help you better.

My domain is: http://watchstore247.com

I ran this command: Not applicable

It produced this output: Not applicable

My web server is (include version): Not applicable

The operating system my web server runs on is (include version): Windows 10 Home 64-bit latest version

My hosting provider, if applicable, is: namesile.com, but running domain on Shopify

I can login to a root shell on my machine (yes or no, or I don’t know): I don’t know

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Not a control panel, but I can change DNS settings, DS records etc.

the http redirection fails, as it redirects to "www" and then back to itself (all via http) on and on and on, back and forth in an endless loop; as shown below:

wget http://watchstore247.com
--2017-07-30 15:10:13-- http://watchstore247.com/
Resolving watchstore247.com (watchstore247.com)... 167.114.213.199, 23.227.38.32
Connecting to watchstore247.com (watchstore247.com)|167.114.213.199|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.watchstore247.com/ [following]
--2017-07-30 15:10:14-- http://www.watchstore247.com/
Resolving www.watchstore247.com (www.watchstore247.com)... 23.227.38.64
Connecting to www.watchstore247.com (www.watchstore247.com)|23.227.38.64|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://watchstore247.com/ [following]
--2017-07-30 15:10:14-- http://watchstore247.com/
Connecting to watchstore247.com (watchstore247.com)|167.114.213.199|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.watchstore247.com/ [following]
--2017-07-30 15:10:14-- http://www.watchstore247.com/
Connecting to www.watchstore247.com (www.watchstore247.com)|23.227.38.64|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://watchstore247.com/ [following]
--2017-07-30 15:10:14-- http://watchstore247.com/
Connecting to watchstore247.com (watchstore247.com)|167.114.213.199|:80... connected.

nslookup watchstore247.com
Addresses: 23.227.38.32
167.114.213.199

nslookup www.watchstore247.com
Name: shops.myshopify.com
Address: 23.227.38.64
Aliases: www.watchstore247.com

openssl s_client -connect 167.114.213.199:443
no response

openssl s_client -connect 23.227.38.32:443
subject=/C=CA/ST=Ontario/L=Ottawa/O=Shopify Inc./CN=*.myshopify.com
issuer=/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA

If your site is ran on a "shared hosting" server, provided by some kind of provider, this provider should be the one to enable you to use SSL. This can be in the form of just a button to get a Let's Encrypt certificate (some providers have integrated Let's Encrypt very well) or, less ideal, provide some kind of way to upload the private key and certificate to your site.

If you have some kind of (virtual) private server, you could use a client yourself, such as certbot.

Thanks for your reply. Osiris.

This is what my domain supplier says: https://www.namesilo.com/Support/Why-we-do-not-offer-SSL%2FTLS-certificates

I have a redirect to Shopify, who provide the hosting.

Thanks, Rudy. It looks like I have two problems to solve. How can the redirect problem be solved? I have to redirect to enable my Shopify site.

The hosting provider should provide some way to install a certificate. The domain supplier doesn’t have anything to do with the actual certificates.

See for more info: https://help.shopify.com/manual/domains/ssl

OK then. So if I am using Shopify for hosting, can I use ‘Let’s Encrypt’ to create the certificate?

See: https://help.shopify.com/manual/domains/ssl

This is what my domain management area looks like:

watch-store-24-7.myshopify.com
OK
watchstore247.com
OK SSL unavailable

www.watchstore247.com
OK

I’ll need to find out why SSL is unavailable for the middle one.

When I use the ‘www’ option I get:

'400 Bad Request

Request Header Or Cookie Too Large
nginx’

I would advice to take this up with your hosting provider.

This depends largely on what your use is for the two sites (IPs).
If you only need one site (shopify), then redirect everything to it.
If you need separate sites, then you need separate names for them.
In any case, you should probably have unique names that resolve to each IP individually.
At this time you have one name that resolves to one IP and another name that resolve to both IPs.
So the first thing to fix is DNS.
My opinion:
Keep "watchstore247.com" & "www.watchstore247.com" to your IP and send any "store" related requests to "watch-store-24-7.myshopify.com".

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.