# SSL Turned on, but "not secure" when browsing

**URL:** <https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492>\
**Category:** RapidWeaver Classic\
**Created:** [February 22, 2024, 5:45pm UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492 "2024-02-22T17:45:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![hdbaumeister](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/hdbaumeister/32/16057_2.png) [@hdbaumeister](https://forums.realmacsoftware.com/u/hdbaumeister)\
**Post date:** [February 22, 2024, 5:45pm UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/1 "2024-02-22T17:45:10Z")

</div>

Hi, all, something broke my https connection - unfortunately, I don’t know what did it.

When I visit [https://www.miraverde.de](https://www.miraverde.de) I get a “not secure” (or similar) notification in Safari (in Firefox, it’s just a crossed-out lock symbol).  
I’ve looked everywhere - I have not http:// references. Period.  
However, if I check the page with Firefox developer view, it shows me that there are plenty of [http://loads](http://loads):

 ![SCR-20240222-qitz](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/8/4/84cc7a3510ee05d380c43c7024d2a95c7c4b5606.png)

Oddly, the Brave browser tells me the site is secure and the certificate valid… I have cleared the cache on both Firefox + Safari… still getting a “not secure” warning.

I’m completely lost here, does anyone have any ideas?  
Thank you!

---

<div class="post-metadata">

**Author:** ![britinusa](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/britinusa/32/9530_2.png) [@britinusa](https://forums.realmacsoftware.com/u/britinusa)\
**Post date:** [February 22, 2024, 7:45pm UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/2 "2024-02-22T19:45:51Z")

</div>

I just checked your site using Safari and it shows a valid certificate. The lock symbol displays correctly.

 ![Screenshot 2024-02-22 at 12.45.33 PM](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/b/f/bfa33cdd10b788125d5ea07bf1b6d458a2481f12.png)

---

<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:** [February 22, 2024, 8:12pm UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/3 "2024-02-22T20:12:41Z")

</div>

Looks secure as long as you get there via an HTTPS call.  
`https://www.miraverde.de/`  
However, you can still get there with a straight HTTP URL  
`http://www.miraverde.de/`  
You should redirect all http calls to https using an htaccess fill.

---

<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:** [February 23, 2024, 6:45am UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/4 "2024-02-23T06:45:44Z")

</div>

> [@hdbaumeister](#):
>
> [https://www.miraverde.de](https://www.miraverde.de)

Run the site through [https://www.whynopadlock.com/](https://www.whynopadlock.com/)

It will give you the code for your .htaccess file to force https and that should fix the issue.

---

<div class="post-metadata">

**Author:** ![hdbaumeister](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/hdbaumeister/32/16057_2.png) [@hdbaumeister](https://forums.realmacsoftware.com/u/hdbaumeister)\
**Post date:** [February 23, 2024, 7:55am UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/5 "2024-02-23T07:55:18Z")

</div>

Fantastic, thank you so much, Doug!  
For some reason, the .htaccess file disappeared and the edit window in RapidWeaver was empty. I was able to roll back to the previous version within RapidWeaver, so I’m assuming something happened to it during an update. Very odd, but you saved the day!  
BR Nick

---

<div class="post-metadata">

**Author:** ![hdbaumeister](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/hdbaumeister/32/16057_2.png) [@hdbaumeister](https://forums.realmacsoftware.com/u/hdbaumeister)\
**Post date:** [February 23, 2024, 7:57am UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/6 "2024-02-23T07:57:17Z")

</div>

Thank you for checking - very odd indeed, that some browsers will show SSL working and some not.  
The issue was caused by a missing .htaccess file.

---

<div class="post-metadata">

**Author:** ![hdbaumeister](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/hdbaumeister/32/16057_2.png) [@hdbaumeister](https://forums.realmacsoftware.com/u/hdbaumeister)\
**Post date:** [February 23, 2024, 8:04am UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/7 "2024-02-23T08:04:55Z")

</div>

Hey Rob, thank you for the URL, that site is new to me.  
It generates a very specific .htaccess file. My “old” one was more generic, but seemed to do the trick (when available, LOL):

```auto
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

```

---

<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:** [February 23, 2024, 8:51am UTC](https://forums.realmacsoftware.com/t/ssl-turned-on-but-not-secure-when-browsing/42492/8 "2024-02-23T08:51:39Z")

</div>

It’s a great site. I used to use it all the time.
