Review M-Files on G2 & get a $25 gift card Arrow right Review us!

Options
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 12 subscribers
  • Views 2811 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL Connection Error per REST API

Niklas Flaspöhler

Hi all,

 

for some of our customers, we try to connect to a vault via POST request using the M-Files Rest API.

We get the following error message "SSL Connection could not be established". Yesterday it still worked.

 

The problem only occurs with vaults in the new cloud environment. It works for vaults in the old cloud and on-premises vaults.

 

Is there any difference in SSL connection between new cloud, old cloud and on-premises? What else can cause the problem?

Has anything been changed in the last few days?

 

The request URL is as follows

/REST/server/authenticationtokens

Parents Reply Children
  • 0 in reply to PapaCho

    Can you give details on the error message?

    There are a variety of reasons for this, but they all boil down to the client and server being unable to negotiate a protocol to use. If this is an existing application and vault then please raise a support ticket.  If this is a new application then you need to check the full error stack to see what is wrong; it's probable that you need to enable some newer protocol support somewhere.

  • 0 in reply to Craig Hawker

    I'll raise a ticket. The error is:

    The SSL connection could not be established, see inner exception. The SSL connection could not be established, see inner exception. The remote certificate is invalid because of errors in the certificate chain: PartialChain 

  • 0 in reply to PapaCho

    So the issue is that your system cannot validate - or does not trust - one of the certificates in the chain.

    Support may be able to guide you on whether there have been some changes.

  • 0 in reply to Craig Hawker

    Surprising to happen suddenly today while this API integration has been running fine for years now

  • 0 in reply to PapaCho

    Me too, but certificates do get changed on servers, and trusted certification authorities also change even in Windows.  You can often use a browser to take a look at the certification chain that's used, and maybe you can use that to cross-reference why your application doesn't trust a part of the chain any more.

M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.