Certificate error on web server on IIS 7.5

Hello experts.
I installed new certificate (from Verisign) on my two servers.
Now they works, but  https://ssl-tools.verisign.com/#certChecker  shows some errors.


Certificate Chain Information
Could not determine the primary certificate for the Web server.

Server Name: online2.ameriabank.am
was checked using port number 443
The certificate installation checker connected to the Web server and read its certificates, but could not determine which is the primary certificate for the Web server. Make sure that the domain name entered above matches the common name of the certificate installed on the Web server.

""
please assist what can I do?
ameriaadminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

emadallanCommented:
you shoud add the verisign cert to your trusted root certificate on both servers
ameriaadminAuthor Commented:
I have don it, the sites work properly, but   https://ssl-tools.verisign.com/#certChecker shows error.
my sites are
online.ameriabank.am
online2.ameriabank.am
emadallanCommented:
could you tell me the error message?
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

ameriaadminAuthor Commented:
I have post it.
<<<
online.ameriabank.am was checked using port number 443
The certificate installation checker connected to the Web server and read its certificates, but could not determine which is the primary certificate for the Web server. Make sure that the domain name entered above matches the common name of the certificate installed on the Web server.
>>>

you can check it by   https://ssl-tools.verisign.com/#certChecker   for onlin.ameriabank.am and online2.ameriabank.am
emadallanCommented:
ok, the problem is due to intermediate certificate called: (VeriSign Class 3 Public Primary Certification Authority - G5) of virisign which is not trusted by verisign, so the solution is replace it in your browser.
please go to :
https://www.verisign.com/support/verisign-intermediate-ca/secure-site-pro-intermediate/index.html
then follow the instructions here:
https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=SO18688
ameriaadminAuthor Commented:
and what to do in server side?
ameriaadminAuthor Commented:
I have replaced VeriSign Class 3 Public Primary Certification Authority - G5, by the new one, but I get same error.
emadallanCommented:
it's browser side, because your problem is that the intermediate cert in the chain is not trusted, contact the virisign and tell them to include the updated intermediate cert in your cert then import it to your two servers.
emadallanCommented:
one thing to mention is: To get browsers to trust the root CA, and intermedite ca the user must install the certificate in the browser's authorities store. so try to install the updated intermedite CA in the IE througn internet options-- import
ameriaadminAuthor Commented:
do you see the errors from https://ssl-tools.verisign.com/#certChecker for online.ameriabank.am and online2.ameriabank.am ?
emadallanCommented:
no, but i just did! i see that now we have two problems:
the first that we talked before
the second is online2.ameriabank.am is not included in you cert as a common name,  why? because Typically a standard secure server SSL Certificate is issued to a single Fully Qualified Domain Name only, which is online.ameriabank.am to which it has been issued. so online2.ameriabank.am is not included.
the solution is to obtain the Wildcard SSL which easily get around this restriction by receiving a Wildcard SSL Certificate issued to *.ameriabank.am. The * character replaces a "fixed" sub-domain with a "variable" one.

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
ameriaadminAuthor Commented:
we already obtained SSL Certificate for online and onlin2 you can see it by opening onlin.ameriabank.am and online2.ameriabank.am
ameriaadminAuthor Commented:
no, but i just did! i see that now we have two problems:
the first that we talked before
the second is online2.ameriabank.am is not included in you cert as a common name,  why? because Typically a standard secure server SSL Certificate is issued to a single Fully Qualified Domain Name only, which is online.ameriabank.am to which it has been issued. so online2.ameriabank.am is not included.
the solution is to obtain the Wildcard SSL which easily get around this restriction by receiving a Wildcard SSL Certificate issued to *.ameriabank.am. The * character replaces a "fixed" sub-domain with a "variable" one.
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
Microsoft Legacy OS

From novice to tech pro — start learning today.