Issues with HTTPS non-www to HTTPS www (or whatever subdomain used for HubSpot) Forwarding

We recently enabled the SSL functionality on our COS. Our domain is storyblock.media and our HubSpot COS URI is https://www.storyblock.media. We use GoDaddy as a domain registrar and we have forwarding setup to forward (http://storyblock.media and http://www.storyblock.media) to https://www.storyblock.media. However, the issue is found when going to https://storyblock.media. It does not forward to https://www.storyblock.media. Instead, the browser loads a blank screen with an error message.

Why? When you setup domain forwarding, visitors technically visit an IP address on GoDaddy's server first that 301 redirects them to the desired destination that's setup in domain/dns settings. This does not work for HTTPS traffic since this GoDaddy server does not have a valid SSL cert for the domain. Therefore, when you attempt to redirect HTTPS traffic via this method, it bellyflops and doesn't go anywhere...

Why is this an issue? Everyone is used to chopping off the www. Chances are they will also chop off the https too, but when they do not, they are not going to end up where they want to go. Who knows. This might result in a few lost backlinks too. Haven't thought out any other SEO issues/implications yet.

That's the problem. Open to others' solutions. Here are two ideas I've had:

1) I can relatively easily setup an SSL cert on my own server with it's only purpose to forward HTTPS non-www to HTTPS www, but that would cost $$ and not solve everyone's issue.

2) HubSpot could setup an IP address to point naked domains to and direct the traffic accordingly (I'm not 100% on how things are setup on their end -- I know there are reasons they utilize the cname setup, but forget why exactly.).

HubSpot updates
23 Replies
MariuszZysk
New Contributor

 Hi, how did you solve this issue Smiley Happy?


@VictoriaGumaer wrote:

We recently enabled the SSL functionality on our COS. Our domain is storyblock.media and our HubSpot COS URI is https://www.storyblock.media. We use GoDaddy as a domain registrar and we have forwarding setup to forward (http://storyblock.media and http://www.storyblock.media) to https://www.storyblock.media. However, the issue is found when going to https://storyblock.media. It does not forward to https://www.storyblock.media. Instead, the browser loads a blank screen with an error message.

Why? When you setup domain forwarding, visitors technically visit an IP address on GoDaddy's server first that 301 redirects them to the desired destination that's setup in domain/dns settings. This does not work for HTTPS traffic since this GoDaddy server does not have a valid SSL cert for the domain. Therefore, when you attempt to redirect HTTPS traffic via this method, it bellyflops and doesn't go anywhere...

Why is this an issue? Everyone is used to chopping off the www. Chances are they will also chop off the https too, but when they do not, they are not going to end up where they want to go. Who knows. This might result in a few lost backlinks too. Haven't thought out any other SEO issues/implications yet.

That's the problem. Open to others' solutions. Here are two ideas I've had:

1) I can relatively easily setup an SSL cert on my own server with it's only purpose to forward HTTPS non-www to HTTPS www, but that would cost $$ and not solve everyone's issue.

2) HubSpot could setup an IP address to point naked domains to and direct the traffic accordingly (I'm not 100% on how things are setup on their end -- I know there are reasons they utilize the cname setup, but forget why exactly.).




manzoor
New Contributor

I spoke to Hubspot about this issue few times and apparently, it cannot be solved. The problem is because the SSL certificate is issued only for your domain name that includes the WWW and not a non-WWW. Rest assured, this issue does not affect your site's SEO ranking. Your WWW website version still gets indexed by search engines and is accessible to all users.

gil100
Top Contributor

 This is really annoying, we get error report also from SEMrush

mkeenan
Occasional Contributor

We also work off root domains and a sub-domain for our blog (not including www.).

 

Has there been any progress towards solving this?

TAOcompany
New Contributor

I have the same issue with www.taocompany.com. I wish there was a solution.. Otherwise we have to switch back to a WordPress website -_-

LPM
Top Contributor

 This is a common issue. If you haven't yet done so, you can point your non-www domain to a server with a htaccess and do a redirect from there.

 

Content would be something along the lines of:

 

RewriteEngine On

RewriteCond %{HTTP_HOST} ^*domain.com*$
RewriteRule (.*) https://www.domain.com/$1 [R=301,L]

 

The common mistake is when people register their domain as the non-www where it should've been setup as an alias instead.

manzoor
New Contributor

@LPM the method you posted will not work on Hubspot. Hubspot does not give access to the .htaccess file. 

LPM
Top Contributor

@manzoor no no, you misunderstand.

 

My point is you need to point your non-www domain to a DIFFERENT server. 

 

Then add a .htaccess to that server to perform the redirection from non-www to https-www.  

LC-Matt
New Contributor

@LPM - Aren't you also forgetting to mention that the "different server" needs a valid SSL certificate on it before it can even accept the request to perform the redirect?  This is the only way I could get it to work...

LPM
Top Contributor

@LC-Matt that's only if the user forces https when they enter the domain.

Usually when people enter an address they will simple type domain.com into the address bar which will lead it straight to the correct redirect.

 

but yes if you want https://domain.com to be forwarded as well you would need to set up an SSL on that server.

 

LC-Matt
New Contributor

@LPM - Given the amount of support requests being generated since moving to hubspot i have a lot of folks that either manually type https before the root domain or they all bookmarked it when that used to be our primary.  

 

I'm actually wondering if we migrated wrong and hubspot should have setup our main site as the apex / root domain instead of the www subdomain. Had they done that I could have done a DNS CNAME redirct on the www record and not even had to deal with SSL redirection.  Old site hosted on wordpress was just the root domain. We even had www being redirected to the root domain.  Hubspot was setup the opposite (by the integrator we used that was quickly clueless shortly after migration).

LPM
Top Contributor

@LC-Matt yeah it's more of a hassle than it should be. Luckily for my site, we never had an SSL (we also changed domains recently) so I'm making do with just redirecting non-www to https www without any issues.

 

As for non-www redirect, you can also set up a conf file on your server (whether apache or nginx)  and set up separate configs for ports 80 and 443, then do the redirection from within the config, or do it with the .htaccess file within the directory you point to within the config.

bendonahower
Regular Contributor

Yep! Would love to see a more elegant solution here.

mscribetech
New Contributor

We are having the same problem. Hubspot support people have no idea what to even say. They keep asking us to coordinate with GoDaddy. One of them also suggested 'nowadays no one type a website without www'!! Very frustrating!!

 

We are with Hubspot since 2012. But Support is so bad now that we are thinking to move out. Any suggestions?

Harris
Occasional Contributor

They do have a support article on this with three possible solutions:

https://knowledge.hubspot.com/articles/kcs_article/cos-general/root-domain-not-loading-https

 

  • Use a third-party service, such as EasyRedir, that provides this functionality. EasyRedir also has a support team to help along the way.
  • Find a DNS provider that supports this functionality.
  • Purchase a server, install an SSL certificate on that server, and configure that server to forward traffic from the secure apex domain.
sarahellis
New Contributor

EasyRedir is happy to help walk through this process for all HubSpot customers. We have online chat support in the bottom right corner of our site, and we're all well versed on this specific URL redirection need. We can help provide information to get set up quickly and our automatic SSL provisioning and renewal means you don't have to worry about this certificate update in future. Please simply identify yourself as a HubSpot customer and we'll help support a seamless transition. 

 

 

Sarah 

VP Business Development, EasyRedir 

LPM
Top Contributor

for those who are tech savvy enough, you can rent your own server for about $5 a month and point your ip there and do the redirect, and use certbot to make yourself a free ssl for the Https redirect.

alt36
Occasional Contributor

And for those of us who arent savvy enough? I need a simple solution to what seems to be a simple problem. Ugh. 

EmmettHughes
New Contributor

The issue with all of this, to me, is that we're paying or asking our clients to pay top dollar for HubSpot and then we have to ask them to shell out more money to solve this problem. You'd think HubSpot could build a server to handle this issue for their customers. Seems like a no brainer.

Aeroll
New Contributor

Hello do you have updates on this one?

Regards,

Aeroll Salcedo