Http to https .htaccess redirect not working in certain browsers suddenly

Help
1

I use htaccess to redirect http to https traffic to my sites. It's been working fine for years.
Recently, I noticed Safari and Chrome do not route http versions of my site to https, but oddly FireFox does. I also noticed http to https redirects are not working in social media browsers (facebook/instagram). Below is my httaccess which has been in production for years. Could it be related to the actual Let's Encrypt recent insurance SSL certificate and browsers?

My htaccess Which redirects http to https (including www.) on example site:

RewriteEngine on
RewriteCond %{HTTPS} !=on [OR]
RewriteCond %{HTTP_HOST} ^www.classicb96.com$ [NC]
RewriteRule ^(.*)$ https://classicb96.com/$1 [L,R=301]

You can test the behavior yourself (Chrome/Safari: http://classicb96.com not resolving. Firefox: http://classicb96.com --> https://classicb96.com)

2

My guess is your port 80 is closed so HTTP cannot be used.

Some browsers initially use HTTPS (port 443) and others don't

But, this really has nothing to do with your Let's Encrypt certificate. This is routine server configuration

3 Likes
4

You were correct! I use a web stack for hosting, I poked around and noticed Apache was running on port 81...WTF! Reason is, I did a system update and it has a version of Apache built in which was re-enabled unknown to me. Disabled that and i'm back working. Thank you so much

3 Likes
5

I had no doubt :slight_smile:

2 Likes
6

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