You are viewing limited content. For full access, please sign in.

Question

Question

SSL Host Name Does Not Match Certificate Host Name

Laserfiche
Updated April 14, 2014
asked on April 11, 2014

Laserfiche Content Repository Server v9.0.2 build 671

 

When I attach a repository and check SSL, the client will login just fine but when I try to login to the same repository on the same machine using the Admin Console, I get this nasty gram:

 

 

Error Code: 1364
Error Message: SSL host name does not match certificate host name. [1364]

------------ Technical Details ------------

LFSO:
    Additional Details:
        ERROR: 1364 (TestSSLError, LFSession.cpp:986)
         (LFSO/9.0.3.777)
LFAdmin.dll (9.0.3.798):
    Call Stack: (Current)
        CDatabaseNode::ShowLoginDialog2
    Call History:
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo
         CComponentData::GetDisplayInfo

 

What information should I give the Systems Group that would guide them to fixing the problem?

 

Thanks in advance. 

 

Dennis

0 0

Answer

APPROVED ANSWER
replied on April 11, 2014

Hi Chad and Brian...

Thanks for the response....I believe that I see the problem now.  The Systems Group set up a cluster that is collectively called LFAPPSVR with nodes LaserficheA (currently offline) and our production server LaserficheB which is online.

 

Looks like they have the certificate generated with LFAPPSVR

 

In the Admin Console, the server referenced is LaserficheB.  When I use the client to attach a repository and choose LaserficheB+SSL I get the nasty gram: SSL host name does not match.....

(LaserficheA is offline so it doesn't count).

 

So, I changed the referenced server in Admin Console from LaserficheB to LFAPPSVR and I am able to login using SSL using Admin Console and Client.

 

Thanks again.

 

0 0

Replies

replied on April 11, 2014

Are you using a different name for the server when attaching this way? Make sure you are using the same name you use when you attach the client.

0 0
replied on April 11, 2014 • Show version history

I would guess that the certificate has the server's FQDN but the server is registered in the admin console with just the host name (or possibly vice versa).  Try re-registering with the FQDN.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...