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

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

  • I'm unaware of any specific changes that were made in the cloud environments over the last 24 hours that could cause this.  Normally when you get an error like this there's some more information (some more detail on why it was not established) that is useful.

    If you go to the web site using a browser does it work?  You say "only occurs with vaults in the new cloud environment"; so this is affecting multiple?

  • Feel free to send me a private message with more information if you cannot post it publicly.

  • Yes, we can connect to the web site using a browser.

    This error occurs with all New Cloud Vaults we tried.

    I will send you a private message with some more information.

  • I had a call with Niklas.

    I'd be interested to hear if anyone else is having similar issues.  We currently think that the problem is elsewhere, but it'd be good to know if other people are suddenly also getting issues.

  • Hello
    I do have the SSL error from today and my M-Files cloud is not migrated to the new Cloud yet

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

  • 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 

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

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

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

1 2