SOLVED - Modify .htaccess file for https

RapidWeaver Classic
21

This would not be related to your google issue. We will get it resolved. Please hang tight while I work on your account.

Thanks for your patience.

22

Yeah, you’re not reading it, or you would get a 500 internal error.

  • Make sure it is called .htaccess (with the dot)
  • Make sure it is “plain text.”
  • It sounds like it is in the right place
  • Are you using CloudFlare?
23

okay, the .htaccess file is being parsed. The fix is simple, sorry I had forgotten. Simply changing the code to:

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

fixed the issue. :slight_smile:

1 Like
24

What port are you running it on? 80 is standard for HTTP, 443 for HTTPS.

25

Pretty sure I have 80 set as well…

26

Might be causing your problem with redirects you thought was cloud flare.

1 Like
27

Occurred to me once I saw that… I didn’t change anything except CF and I added a robots.txt that just blocks one page. Greg will hopefully let me know.

28

Maybe something changed at CDog.

1 Like
29

I have modified my response in order to avoid confusing users. Please disregard. No, this has nothing do with @LSPhoto CloudFlare issues.

1 Like
30

A little context for you, a feature of Chillidog users is that we automatically accelerate a user’s website. This is different than Apache. Sorry for the confusion :slight_smile:

31

Thanks @barchard.

So going forward if I keep a note of these three lines and replace www.domainname.com with the relevant URL each time, then that’ll work for new sites on CDog?

Rob

2 Likes
32

yes, plus the code is far more robust and would work on other hosts too. RewriteCond %{SERVER_PORT} 80 is the older style of doing this

2 Likes
33

Sorry to hijack this post, but thanks to @barchard, who also cleared up a problem I was having with Cloudflare.
Love my Chillidog!