troubleshooting Question

Browser doesn't like https://domainname.com but accepts https://www.domainname.com

Avatar of rascal
rascalFlag for United States of America asked on
SSL / HTTPS
4 Comments1 Solution510 ViewsLast Modified:
We have installed a dedicated SSL certificate (our web host did on our shared web site) for our www.domainname.org. When folks visit https://www.domainname.org they view the site in secure mode no problem.

BUT - there are some google links to our site that link to https://domainname.org (without the www prefix). When users click on that link, they get a security warning from their browser stating that the site was set up for www.domainname.org.

Why is this happening? I understand that the common name assigned to an SSL means that is the specific address that it is for. But I am able to go to my own local web server where I installed a dedicated SSL and I can go to either https://www.mydomain.com or https://mydomain.com and I don't get a security warning.

Why do users clicking on the google link get the security error, but I don't when I go to my local site in SSl mode? Is it because they are clicking on a link, vs. my manually typing it in my browser? That is the only difference I can make out.

Any thoughts?
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 1 Answer and 4 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros