Hi, the domains I’m working on are ontarioadvancedsurgerycenter.com/ and uplandoutpatient.com.
The server is a LAMP stack running Ubuntu 14.04.5
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”.
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
Looks like an own ip address you can manage.
But your source domain:
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
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!
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!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.