Internal users to external website says insecure web page

This morning we came in and internal users are getting the old website is insecure message while outside users can get to the site just fine.  Not sure why. This is our company website.
schmad01Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
if this is only a google chrome issue then it is because of their degradation of the Subject Name part of the Certificate in favour of the  subjectAlternativeName part of the Certificate.  

It in all probability is the different ways in which local machines access the web server vs the way remote machines do.
What you can do is make them equivalent by removing the local CNAME record for www and sitename.xxx.

i.e. you may be accessing www.example.com via webserver.example.com internally but externally you have a port forward from external to internal i.e. tcp port 80 from WAN to the ip address of webserver.example.local

So you have to trace the route and look at what the certificate requires to be true and what the web client is actually getting
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
schmad01Author Commented:
On our internal DNS server we actually have an A record for www.  Should I just delete that?  Do I need it? I think when I deleted it yesterday, internal users got a Cannot Acccess this Web Page message.  We had to change the A record address yesterday also because the website ip address changed.
0
David Johnson, CD, MVPOwnerCommented:
did your A record point to the external or internal address?
0
schmad01Author Commented:
Had to add a Cname record pointing to amazon who issues the cert.  Added a root record also so all is working.
0
schmad01Author Commented:
Had to add a Cname record pointing to amazon who issues the cert.  Added a root record also so all is working, you pointed me in the right direction.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.