<div>
I usually click on the lock in the brower on the address line. &nbsp;What you do next to look at the certificate depends on the browser. &nbsp;(It'll frequently let you know WHY something is untrusted. &nbsp;Candidates include: Certificate not signed by a trusted root; Certificate expired; Certificate signed with a SHA1 signature, etc.)<br />
<br />
From the server, you'll want to bring up the IIS Manager, and drill down to the webpage. &nbsp;Right click, and select 'bindings', and select the https line. &nbsp;It'll display the certificate it's using by it's friendly name. &nbsp;(And to see which certificates are available on the server, close the bindings page, and select the server itself. &nbsp;In the features view, under Security, you'll have an icon for 'Server Certificates'... selecting that will show you the certificates available to IIS in the certificate store.
</div>


<div>
Thanks Rich.<br />
so i looked at the edit bindings for the default website (its the only website) &nbsp;and there is only one for http. &nbsp;there isn't one for <a href="https://" rel="ugc nofollow">https://</a><br />
i also noticed a warning in the top right that says. &nbsp;This site does not have a secure binding (HTTPS) and cannot accept SSL connections.<br />
<br />
any more input from here?
</div>


<div>
so i have tried to add a binding for https to the default website. &nbsp;there are some certificates that are available for me to choose from. &nbsp;One that doesn't expire until 2040. &nbsp;I select it and add the binding....<br />
and it says. &nbsp;this binding is already being used. If you continue etc....... do you want to use this binding anyway. &nbsp;I don't see anything that indicates this binding is already being used in the bindings interface. &nbsp;anybody know what gives?
</div>


<div>
&gt; binding already used...<br />
Aha! &nbsp;Do you have another website on that server that maybe has <a href="https" rel="ugc">https</a>: already bound on port 443? &nbsp;If so, you have a little bit of a problem... in that only one certificate can be bound on a port on the server at a time. &nbsp;:-( &nbsp;(And if you do select okay at that point, you'll likely break the OTHER website, 'cause now it may have a certificate that doesn't correspond to THAT site.)<br />
<br />
On the other hand, if you find which certificate that other website uses... you should be able to use that same certificate on the binding for this website. &nbsp;(And at that point, you may get a certificate mismatch error on your website, but traffic can still be encrypted.)
</div>


<div>
<div class="content wysiwyg-content">
I don't know much about certificate errors. &nbsp;I have an internal App Server that when people go the the internal address (only option anyway)<br />
it gives errors about an untrusted site. &nbsp;How can i tell what security certificate the app/website is using on the server and whats the easiest way to get by this. &nbsp;Unless there is something i am unaware of.... im not really concerned about security certificates on this web server because it is on our lan and not in the dmz.<br />
advice?<br />
<br />
Windows Server 2012<br />
IIS Version 8.5.9600.16384
</div>
</div>


I don't know much about certificate errors.  I have an internal App Server that when people go the the internal address (only option anyway)
it gives errors about an untrusted site.  How can i tell what security certificate the app/website is using on the server and whats the easiest way to get by this.  Unless there is something i am unaware of.... im not really concerned about security certificates on this web server because it is on our lan and not in the dmz.
advice?

Windows Server 2012
IIS Version 8.5.9600.16384

Security Certificate error

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.