# Shout out for Chillidog Hosting

**URL:** <https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356>\
**Category:** RapidWeaver Classic\
**Created:** [October 16, 2016, 2:03pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356 "2016-10-16T14:03:53Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 16, 2016, 2:03pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/1 "2016-10-16T14:03:53Z")

</div>

Just a quick note of thanks to Greg at Chillidog Hosting. A year ago, I created a TMS site for a client that would not run on their current host’s platform (with over 2,000 calls, it exceeded the number allowed). So, I moved them over to a **[Frankfurter account](https://www.chillidoghosting.com/chillidog-hosting-plans-and-pricing/chillidog-hosting-shared-hosting/#)** with Chillidog Hosting. All has been great since.

Over the weekend, I moved another of their sites from a host in Canada that they’ve long been with to the same Chillidog plan (no extra money) so that I’d have total control over the cPanel (databases and email) instead of the FPT privileges I had (the hosting plan was maintained by a previous web designer, who only gave me FTP rights). I then reached out to Greg to find out how much it would cost to install an SSL Certificate. Imagine my surprise when he said “NOTHING - SSL certificates can now be installed for free via the Control Panel.” It was literally one click, and then an hour or so cleaning up the http calls for my warehoused images. BOOM!

So, along with the great service Greg provides, this is just another reason to consider Chillidog for your hosting needs. To contrast, GoDaddy charges $150/year to secure five sites…Chillidog charges zero.

Oh, and yes - the SSL turns the browser bar green!

---

<div class="post-metadata">

**Author:** ![robbeattie](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/robbeattie/32/78_2.png) [@robbeattie](https://forums.realmacsoftware.com/u/robbeattie)\
**Post date:** [October 19, 2016, 4:19pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/2 "2016-10-19T16:19:34Z")

</div>

@dave - I’ve got some sites with CDog, is there a step-by-step anywhere that explains the process of installing the certificate?

Thanks

Rob

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 19, 2016, 5:56pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/3 "2016-10-19T17:56:40Z")

</div>

Hi @robbeattie The process could not have been easier. In your control panel, look for “Let’s encrypt item” Click it and follow the directions (it will take about 30 seconds, lol). The second part involves your site…anything referenced from within your site will need to be with https, not http. So, if you have warehoused images, PDFs, etc., you most likely have the URL set as [http://example.com/xxxxxxxx](http://example.com/xxxxxxxx) You’ll need to update them to [https://example.com/xxxxxxxx](https://example.com/xxxxxxxx) (or, just /xxxxxxxx - although the items won’t preview if you use this method). You’ll know everything is correct when you preview each page in a browser. Safari will show you the padlock, Chrome will show you the padlock in green. If you’re not seeing this, then click on the developer tools and then Show Error Console. You’ll get a list of items that need to be changed to https.

Copying Greg @barchard in case he’d like to add anything.

---

<div class="post-metadata">

**Author:** ![Nigel](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/nigel/32/142_2.png) [@Nigel](https://forums.realmacsoftware.com/u/Nigel)\
**Post date:** [October 19, 2016, 6:12pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/4 "2016-10-19T18:12:35Z")

</div>

I’ve been meaning to take the plunge and go https. Glad it is easy. Did you need to do anything with the theme or stacks or did they just work ‘within’ SSL OK?  
Most of mine is Foundation and other odd bits.

Nigel

---

<div class="post-metadata">

**Author:** ![Nigel](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/nigel/32/142_2.png) [@Nigel](https://forums.realmacsoftware.com/u/Nigel)\
**Post date:** [October 19, 2016, 6:13pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/5 "2016-10-19T18:13:42Z")

</div>

PS. Yes Greg and Chillidog are the best.

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 19, 2016, 6:26pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/6 "2016-10-19T18:26:06Z")

</div>

They should just work. However, I have at least one map stack where choosing a built-in color marker throws an error. Unbelievably, the marker is coming from an http URL owned by none other than Google. I’m guessing they also have an https url that could be accessed, but the developer hasn’t updated his stack. I got around it by using my own location pin rather than the one offered in the map stack.

---

<div class="post-metadata">

**Author:** ![barchard](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/barchard/32/2292_2.png) [@barchard](https://forums.realmacsoftware.com/u/barchard)\
**Post date:** [October 19, 2016, 6:33pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/7 "2016-10-19T18:33:11Z")

</div>

Nope, that’s pretty good. I had a blog post on this but the Ghost app I was using/trying is broken. _sigh_ time to re-set things up 🙂

@robbeattie no guide at the moment, but working to re-do all of my documentation on the hosting side of things.

-greg

---

<div class="post-metadata">

**Author:** ![Nigel](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/nigel/32/142_2.png) [@Nigel](https://forums.realmacsoftware.com/u/Nigel)\
**Post date:** [October 19, 2016, 8:05pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/8 "2016-10-19T20:05:40Z")

</div>

Cheers. Will be converting to SSL as a winter project.

---

<div class="post-metadata">

**Author:** ![robbeattie](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/robbeattie/32/78_2.png) [@robbeattie](https://forums.realmacsoftware.com/u/robbeattie)\
**Post date:** [October 20, 2016, 11:52am UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/9 "2016-10-20T11:52:09Z")

</div>

Hi @dave, I have a related question.

I’ve installed the certificate and if I type [https://www.theblackpike.com](https://www.theblackpike.com) into Safari then it comes up fine, padlock and all.

But if I type [www.theblackpike.com](http://www.theblackpike.com) - which is what I’d expect a visitor to type - then the padlock doesn’t appear. There’s obviously a step I haven’t completed?

Any advice appreciated.

Thanks

Rob

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 20, 2016, 1:24pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/10 "2016-10-20T13:24:50Z")

</div>

Hi @robbeattie It looks like your favicon is not being found - perhaps that’s causing the error? I’ve copied @barchard for his expertise. Your site looks great, by the way!

 ![](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/2X/a/a9ef061075cf564f99ceffb6b9adc9dc2bb542f6.png)

---

<div class="post-metadata">

**Author:** ![barchard](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/barchard/32/2292_2.png) [@barchard](https://forums.realmacsoftware.com/u/barchard)\
**Post date:** [October 20, 2016, 1:41pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/11 "2016-10-20T13:41:18Z")

</div>

browsers default to `http://`, not `https://`. you will need to force a redirection from `http` to `https`. I recommend using a `.htaccess` file:

```auto
RewriteEngine On 
RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteCond %{SERVER_PORT} 80 
RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]

```

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 20, 2016, 1:54pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/12 "2016-10-20T13:54:02Z")

</div>

Not knowing much about how this code works, I’ve been using the following. Would you recommend I switch it?

RewriteEngine On  
RewriteCond %{HTTPS} off  
RewriteRule (.\*) https://%{HTTP\_HOST}%{REQUEST\_URI}

---

<div class="post-metadata">

**Author:** ![barchard](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/barchard/32/2292_2.png) [@barchard](https://forums.realmacsoftware.com/u/barchard)\
**Post date:** [October 20, 2016, 2:05pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/13 "2016-10-20T14:05:14Z")

</div>

if it ain’t broke, don’t fix it 😛

---

<div class="post-metadata">

**Author:** ![robbeattie](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/robbeattie/32/78_2.png) [@robbeattie](https://forums.realmacsoftware.com/u/robbeattie)\
**Post date:** [October 20, 2016, 2:39pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/14 "2016-10-20T14:39:30Z")

</div>

> [@barchard](#):
>
> RewriteEngine On  
> RewriteCond %{HTTP\_HOST} ^example.com [NC]  
> RewriteCond %{SERVER\_PORT} 80  
> RewriteRule ^(.\*)$ [https://www.example.com/$1](https://www.example.com/$1) [R,L]

So to be clear, for my site I’d open the .htaccess file and change this to:

RewriteEngine On  
RewriteCond %{HTTP\_HOST} ^theblackpike.com [NC]  
RewriteCond %{SERVER\_PORT} 80  
RewriteRule ^(.\*)$ [https://www.theblackpike.com/$1](https://www.theblackpike.com/$1) [R,L]

Does it have to go anywhere in particular - at the top or the end?

Thanks

Rob

---

<div class="post-metadata">

**Author:** ![robbeattie](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/robbeattie/32/78_2.png) [@robbeattie](https://forums.realmacsoftware.com/u/robbeattie)\
**Post date:** [October 20, 2016, 2:40pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/15 "2016-10-20T14:40:24Z")

</div>

@dave - thanks for the kind words about the site. I’m re-building it in Foundation and it’s been fun so far.

Rob

---

<div class="post-metadata">

**Author:** ![barchard](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/barchard/32/2292_2.png) [@barchard](https://forums.realmacsoftware.com/u/barchard)\
**Post date:** [October 20, 2016, 2:56pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/16 "2016-10-20T14:56:51Z")

</div>

at the top would be preferable and make the most sense.

---

<div class="post-metadata">

**Author:** ![robbeattie](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/robbeattie/32/78_2.png) [@robbeattie](https://forums.realmacsoftware.com/u/robbeattie)\
**Post date:** [October 20, 2016, 3:17pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/17 "2016-10-20T15:17:32Z")

</div>

It’s not working for me I’m afraid. I’ll raise a support ticket because this would be really useful for me to understand going forward.

Thanks to both.

Rob

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 20, 2016, 3:31pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/18 "2016-10-20T15:31:32Z")

</div>

If you haven’t already, please try the code I posted above too…I’m using it successfully on a site hosted by Chillidog. Also, if you haven’t done so, please either place a favicon in the right directory or remove that line from your index file.

---

<div class="post-metadata">

**Author:** ![teefers](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/teefers/32/8173_2.png) [@teefers](https://forums.realmacsoftware.com/u/teefers)\
**Post date:** [October 20, 2016, 6:41pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/19 "2016-10-20T18:41:06Z")

</div>

Here is one that should work as well:  
RewriteEngine On  
RewriteCond %{SERVER\_PORT} 80  
RewriteRule ^(.\*)$ [https://www.example.com/$1](https://www.example.com/%241) [R,L]

Change example to your site.

.htacess files can be a bear to test so here is a simple tester site:  
[http://htaccess.madewithlove.be](http://htaccess.madewithlove.be)

---

<div class="post-metadata">

**Author:** ![dave](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dave/32/147_2.png) [@dave](https://forums.realmacsoftware.com/u/dave)\
**Post date:** [October 22, 2016, 3:08pm UTC](https://forums.realmacsoftware.com/t/shout-out-for-chillidog-hosting/10356/20 "2016-10-22T15:08:36Z")

</div>

This rule is working as well - it not only forces https, but also strips out www

```
 RewriteCond %{HTTPS} off
 RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
 RewriteRule .* https://%1%{REQUEST_URI} [R=301,L]
 RewriteCond %{HTTPS} off
 RewriteCond %{HTTP_HOST} !^www\. [NC]
 RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
 RewriteCond %{HTTPS} on
 RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
 RewriteRule .* https://%1%{REQUEST_URI} [R=301,L]
```
