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

Reply
  • 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?

Children