Redirecting with https protocol

[Kaplan]

Hi, the domains I’m working on are ontarioadvancedsurgerycenter.com/ and uplandoutpatient.com.

The server is a LAMP stack running Ubuntu 14.04.5
certbot 0.22.2

I’m trying to redirect uplandoutpatient.com to ontarioadvancedsurgerycenter.com and I have that working, but I am unable to redirect if someone uses a domain with the protocol https://uplandoutpatient.com and https://www.uplandoutpatient.com.

I’ve tried a few different approaches but I’m unable to make a certificate for uplandoutpatient.com. I don’t have access to the domain name management and I think my client might be redirecting there.

I tried adding the other domains when I create the certificate but I’m getting errors.

sudo certbot --apache -d ontarioadvancedsurgerycenter.com -d www.ontarioadvancedsurgerycenter.com -d uplandoutpatient.com

Any advice or suggestions for redirecting with protocol? The issue is a Google search on Upland brings back the address with the protocol and then I get the “Warning: Potential Security Risk Ahead”.

Thanks,
Dave

[JuergenAuer]

Hi @Kaplan

I’m trying to redirect uplandoutpatient.com to ontarioadvancedsurgerycenter.com and I have that working, but I am unable to redirect if someone uses a domain with the protocol https://uplandoutpatient.com and https://www.uplandoutpatient.com.

there is a check of your domain, 30 minutes old - https://check-your-website.server-daten.de/?q=uplandoutpatient.com

There you see the problem.

First checked your destination domain - https://check-your-website.server-daten.de/?q=ontarioadvancedsurgerycenter.com

Host	T	IP-Address	is auth.	∑ Queries	∑ Timeout
ontarioadvancedsurgerycenter.com	A	207.223.115.39 Tuscaloosa/Alabama/United States (US) - TekLinks, Inc. Hostname: 207_223_115_39.colo.teklinks.com	yes	2	0
	AAAA		yes
www.ontarioadvancedsurgerycenter.com	C	ontarioadvancedsurgerycenter.com	yes	1	0
	A	207.223.115.39 Tuscaloosa/Alabama/United States (US) - TekLinks, Inc. Hostname: 207_223_115_39.colo.teklinks.com	yes

Looks like an own ip address you can manage.

But your source domain:

Host	T	IP-Address	is auth.	∑ Queries	∑ Timeout
uplandoutpatient.com	A	184.168.131.241 Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC Hostname: ip-184-168-131-241.ip.secureserver.net	yes	2	0
	AAAA		yes
www.uplandoutpatient.com	C	uplandoutpatient.com	yes	1	0
	A	184.168.131.241 Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC Hostname: ip-184-168-131-241.ip.secureserver.net	yes

That’s a GoDaddy secureserver.net - ip address.

So you can only create GoDaddy-redirects. That works only with http.

• Change the ip address of uplandoutpatient.com to your other ip address.
• Create there a port 80 vHost
• Create a certificate with non-www and www and normal redirects http -> https
• last (and new) step: Create a redirect https + preferred version uplandoutpatient.com -> https + preferred version your other domain

[schoen]

That’s a GoDaddy secureserver.net - ip address.

So you can only create GoDaddy-redirects. That works only with http.

GoDaddy tries to make things really convenient for their users with services like this, but they also really take away the users’ ability to make changes outside of the GoDaddy control panel!

[Kaplan]

You guys are the best! Thank you.

I was able to have my client change the IP address, setup the certificate and handle the redirect by updating the -le-ssl.conf file once everything was working. I’m all set for this one. I have another set of domains like this and should be able to follow the same pattern to get them working. Thanks again!