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

Parents

0 Craig Hawker 11 months ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Craig Hawker 11 months ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 PapaCho 2 months ago in reply to Craig Hawker

Hello
I do have the SSL error from today and my M-Files cloud is not migrated to the new Cloud yet
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 2 months ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 PapaCho 2 months ago 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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 2 months ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 PapaCho 2 months ago in reply to Craig Hawker

Surprising to happen suddenly today while this API integration has been running fine for years now
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Craig Hawker 2 months ago 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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Niklas Flaspöhler 2 months ago in reply to Craig Hawker

Just for your information. As far as i remember in our case the problem was in fact related to another system and not M-Files. Back then Microsoft changed something in their authentication.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel