cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution
New

Deluxe Windows Web Hosting domain forwarding didn't work

I have Deluxe Windows Web Hosting with two websites: indyrunners.org and samcosta.com. I purchased a multiple domain (UCC) SSL from GoDaddy. The domain names are also with GoDaddy. I would like http://samcosta.com, http://www.samcosta.com, and https://samcosta.com to redirect to https://www.samcosta.com (https version with the www subdomain).

 

I believe I have the SSL certificates installed correctly because all of the above links worked. I used the domain name indyrunners.org and SANs: www.samcosta.com, samcosta.com, and www.indyrunners.org.

 

The problem is that I couldn't get the redirect to work. For subdomain forwarding, on the DNS Management Page I added a subdomain of samcosta.com forwarded to https://www.samcosta.com (temporary 302) without masking. When I pressed the "Preview" buton, https://www.samcosta.com was correct, but after saving the change, things didn't work correctly. (I also did the same thing with www.samcosta.com.) If I surfed to http://samcosta.com or https://samcosta.com, I got the message "This site can't be reached". If I surfed to http://www.samcosta.com or https://www.samcosta.com, it redirected to https://www.samcosta.com with the message: "Your connection is not private Attackers might be trying to steal your information from www.samcosta.com (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID". When I clicked "Advanced", I saw "This server could not prove that it is www.samcosta.com; its security certificate is from shortener.secureserver.net." The certificate should say it was issued to indyrunners.org, the primary domain.

 

Since this didn't work, I've since deleted the forwarding.
 

Any suggestions for getting the forwarding to work? Thanks.

2 REPLIES 2
Moderator
Moderator

Re: Deluxe Windows Web Hosting domain forwarding didn't work

Hi @bpc, thanks for posting.

You can't use forwarding in this way to forward the domain name to itself. It will create a redirect loop and cause the error you mentioned.

If you want to redirect users to use HTTPS, you must use some sort of scripting or redirect on your hosting plan. On a Windows plan, this is common done using rewrite rules in a web.config file.

 

Gary - GoDaddy | Community Moderator
24/7 Support | Check System Status
New
Solution

Re: Deluxe Windows Web Hosting domain forwarding didn't work

Thanks. I thought I'd tried it previously, but I eventually got the web.config approach to work last night using https://ph.godaddy.com/help/redirect-my-website-to-https-in-pleskwindows-27873 as a guide and the following code in web.config to both redirect to https: and show www on both websites:

 

<rule name="HTTP to HTTPS redirect">
<match url="(.*)" />
<conditions>
<add input="{HTTPS}" pattern="off" ignoreCase="true" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" />
</rule>
<rule name="Redirect to www subdomain">
<match url=".*" />
<conditions logicalGrouping="MatchAll">
<add input="{HTTP_HOST}" pattern="^(www\.)(.*)$" negate="true" />
<add input="{SERVER_PROTOCOL}" pattern="^(.*)(/.*)?$"/>
</conditions>
<action type="Redirect" url="https://www.{HTTP_HOST}/{R:0}">
</rule>
 
However, I have one final issue. Now, when I surf to samcosta.com, the resulting address shown in Chrome is https://www.samcosta.com/samcosta. The "samcosta" at the end is the folder for that domain. (Again, I have deluxe hosting.) I can't figure out how to get it to display just https://www.samcosta.com using web.config, i.e., get rid of the "samcosta" folder in the web address bar.