https works on all devices. http doesn't work on some mobile browsers and devices

[ralmtech]

Good day

I have a bit of a weird problem that I am not sure I am understanding.

========================

Environment:

========================

Website built with HubSpot web builder (works)

Custom domain bought via GoDaddy (nameserver is local hosting company)

Domain mapped (from HubSpot) to local hosting company - cPanel / Shared hosting

SSL Certificate installed and active

========================

What I am expecting:

========================

When a visitor types the url (or any variation of the domain - example.com) then the domain is redirected to secure connection https://example.com

========================
Here is what is happening (and not working):

========================

One all laptops (HP, Lenovo, MacBook, ASUS), their browsers (Opera, Firefox, Chrome, Edge, Safari) and on different networks (Fibre, 5G,

Mobile Data etc) things work as expected

The problem is on mobile devices and as follows:

iPhone 6s on all networks
- working - Firefox, Chrome, Safari

- not working - Opera, Opera Mini, Opera Gaming

iPhone 8 on all networks

- working - Safari, Chrome

- not working - Opera, Opera Mini, Edge, Firefox

Samsung

- working - Chrome, Samsung Internet

- not working - n/a

Huawei

- working - Chrome, Internet Browser

- not working - n/a

Huawei Mate something or other

- working - Chrome, Browser (native browser, can't remember the name), Opera Mini, Opera

- not working - Opera Gaming, Firefox

iPhone 15

- working - n/a

- not working - Safari, Chrome

========================

FYI (and for clarity):
By "not working" I mean

When I type http://example.com, www.example.com, http://www.example.com 

I get the below error; "This page is unavailable. If you believe this is a mistake, please contact the website owner." The page does not render.

It is important to note that when I explicitely type

https://example.com, https://www.example.com then it works

By "working" I mean

When I type all URL variations then I the website is rendered as expected i.e.; example.com, www.example.com, http://example.com, http://www.example.com, https://example.com, https://www.example.com 
So by "working" no matter what iteration I type, the page is directed to the https connection

========================

Troubleshooting I have done so far

========================

Confirmed custom domain mapping details.

Confirmed valid SSL certificate

Tried different devices, browsers and networks

Reached out to ISP and they confirm all is well on their side

Confirmed "Force Redirect" from http to https

Reached out to HubSpot (and they seem to be just as stumped) awaiting escalated feedback

Many thanks,

[DianaGomez]

Hello @ralmtech, considering that another user: @KeyWestScott  is going through the same issue, could you please share in this thread if you were able to resolve it with the help of HubSpot Support? And how? This way, more people can benefit from the solution if they encounter the same question. 

Thank you,

Diana

[KeyWestScott]

I"ve had similar issues with that as well.  Some folks that enter the naked domain, get the same error that you recieved, but if they enter the fully qualified name, get through.  Redirects are all correct and others on the same network get in just fine....  Cleared cache, DNS caches, etc.....  No go..  Very frustrating.

[DianaGomez]

Hi @ralmtech,

Thank you for sharing such detailed information regarding the HTTPS redirection issue you are experiencing across various devices and browsers. 

The discrepancy in HTTPS redirection behavior among different devices and browsers you've outlined is indeed intriguing. It could be attributed to specific configurations unique to those particular devices or browsers.

Given that you have already sought assistance from  HubSpot support, it is crucial to continue collaborating closely with them to delve deeper into the matter and potentially pinpoint any specific compatibility issues with the devices and browsers that you mentioned.

The question will remain open to the public in case anyone has encountered a similar issue or has any suggestions for you. 

Thank you,

Diana