The problem is when entering the domain without leading https:// in Safari for the first time, it then renders on some (with my tests 2 out or 3) unavailable.
In the screenshot here I have one normal window where I was already logged into Hubspot and then the page rendered and does not even not logged in and one incognito window. The normal one has seemingly the SSL sorted and thus renders the page. I am assuming this is a SSL issue as per the other threads in this community. The incognito window does not render.
Neither does it with other people on Safari.
I have looked into help from Safari side but this error simply is nowhere described. And the error also mentions to contact website owner.
Look at the address bar how they display differently although both entered www.domain.com - so should resolve the same way but doesn't. I suspect the solution can be found in this. Perhaps the redirect is an issue? It is set up correctly and SSL is tested working, it also works in other browsers and even in Safari when that has already once rendered it.
I also verified our website www.worqflow.co and it responds the same as hubspot.com in Safari Private Window, but yours still presents the error.
I spotted this in the Domains & URL settings:
Can you check with your domain provider to see if you already have CAA? If so, adding 0 issue 'pki.goog' is required and could be what's causing the conflict with the SSL (I have no way to confirm this, just something else we can try).
I have actually found quite a few other threads in the community about the same issue (here's one), none of them have solutions unfortunately.
If my reply answered your question please mark it as a solution to make it easier for others to find.
Hi @BettinaHorvath I opened your website in Chrome to verify the URL, then opened it in Safari with the https:// removed and with it included, plus private window.
Safari Private Window requires a protocal (http or https) so entering the URL without one will return an error as you have shown.
I noticed in your screenshot, you wrote that you typed www.whatsyournumbertoday.com/ but your website doesn't contain the www. subdomain (unrelated), but I point this out because you have successfully set up a redirect from www. to non-www. in your DNS.
My suggestion for resolving the issue in Safari would be to configure a DNS redirect from http:// to the https:// version to see if that will resolve the SSL certificate from not being found when entering the URL directly.
You can also submit the HTTPS to Google Search Console to ensure visitors reach the HTTPS version:
My question is - how likely is it that someone manually types your URL in the address bar? are you distributing the URL on radio, in print, etc. where someone might type it in?
Most of the time people arrive at your website from a link, QR code, or Search Results so it would be very unlikely that they could recreate this issue.
If my reply answered your question please mark it as a solution to make it easier for others to find.
I have no idea how to do a "DNS redirect http to https", a search reveals need to access .htacess and no idea how to do that. In previous years when I had WP hosted sites I could just access that via the file manager but how this would work on Hubpost I do not know and according to a surface search on how to do this via DNS reveals that this is not possible. So I'll have to continue the search over the weekend when I have a quiet moment.
I will add this in Google as you suggested maybe it helps.
The typing in was just me to figure out the behavior. when the link is www.whatsyournumbertoday.com and people click it, it doesn't open. That's the problem and how I even noticed. I sent the link to friends to test and they couldn't open the page when they were on Safari (although one could, so there isn't even consistent behavior).
You're welcome @BettinaHorvath, I'm happy to help clarify further.
For the HTTP to HTTPS redirect, you would have to have the HTTP version hosted on HubSpot to congifure it there, which is why using the your domain provider is a little easier (less expensive) - I apologize for the confusion, I typed "DNS" but meant "domain host" (I was typing too quickly).
The DNS just points your website to the right place, but your domain provider should allow you to create domain level redirects.
If you want to share your domain host/provider with me, I can share specific steps for getting it configured.
To your next question, if you want someone to type in www.whatsyournumbertoday.com then you would need to update your domain settings in HubSpot to have the www as a subodmain instead of leaving it blank.
To do this, you would need to disconnect your current domain and reconnect it, adding the www here when you do:
With the www - shouldn't that work anyway because a redirect is setup?
The domain host has a redirect function yes, but also at a price, question is what is cheaper. I am going to go paid on Hubspot, just want to setup everything first, get some content going and once I'm ready to get into marketing mode switch to paid.
Disconnecting and connecting again is not a problem. But does it then still work for the urls without www?
Just to clarify: on Safari whether one includes the www or not, if the protocoll is not included in the link it does not resolve and shows unavailable. So it seems to me that it isn't the issue with or without www. And in Chrome either one works just fine and shows the page with https in front. And even when it's http it redirects to https. So on Chrome it is working as one would expect. Just not on Safari. There is something Safari doesn't like and the question is what.
Hi @BettinaHorvath Thank you for the screenshot, that's really helpful!
I didn't realize you already had a www. redirect configured in HubSpot, so yes, that will take care of it so that both links work.
You're correct, the issue with Safari is regardless of the www.
Chrome automatically looks for the protocol, Safari doesn't.
Safari requires one or the other, if it is blank/missing or something else it won't load the page:
What I would recommend, when you send links, you can configure so that the text reads www.whatsyournumbertoday.com but the link has the protocol - this would avoid the issue altogether:
Adding it as a snippet will make it easy to add to your emails and you should always use the full URL when configuring buttons in marketing emails.
If my reply answered your question please mark it as a solution to make it easier for others to find.
Thx for all your help but the issue remains and is not a Safari problem, otherwise all the other websites wouldn't work either when I only type the top level domain without protocoll and that's not the case. I have in fact never encountered this error before.
So the issue must lie in some setting in Hubspot. When I type in www.hubspot.com the website renders without error and opens with the https protocol. So it should do with mine.
I also verified our website www.worqflow.co and it responds the same as hubspot.com in Safari Private Window, but yours still presents the error.
I spotted this in the Domains & URL settings:
Can you check with your domain provider to see if you already have CAA? If so, adding 0 issue 'pki.goog' is required and could be what's causing the conflict with the SSL (I have no way to confirm this, just something else we can try).
I have actually found quite a few other threads in the community about the same issue (here's one), none of them have solutions unfortunately.
If my reply answered your question please mark it as a solution to make it easier for others to find.
Thx - that was actually my very first initial idea of what is wrong because yes, the domain provider had set up a SSL already. Asked in Hubspot chat about that but since I'm still on the free plan we didn't get anyhwere with this and then I forgot about it going down the rabbit hole in the forum here.
I saw that "help" info field but don't understand it. Where am I supposed to change what exactly? "adding 0 issue 'pki.goog' is required" this a sentence that makes absolutely no sense to me.
What is CAA? The certificate?
I found with the provider an option to download the certificate and private key "to install it on an external server". That is perhaps what this is? I requested this. Seems to take a bit.
But not sure what to do then with it once I can download it.
Can you please help me to add this whatever it is? thx