Skip to main content

Hey all,

 

I'm trying to do some webservice calls with the httpcaller. Unfortunately i'm getting the famous SSL connect error. I've tried setting the 'verify ssl certificate' to no but i'm still getting the error. I'm using FME 2020.1 and as an example i'm trying to do a get on the next endpoint/url:

https://jira.atlassian.com/rest/api/latest/issue/JRA-9

 

My http caller settingssslhttpcallerThe endpoint in the browser gets a nice Json back as response. The httpcaller however doesn't. The certificate is a wildcard certificate (could the be an issue?).

CertificatesCan anyone check it out if it works for them or if they get the same result? Just wondering

 

cheers

Using FME 2019.1.2.1 (that's what i had open) I get a json file when using a HTTPCaller to that URL.

No problems.


Hi @adriaan​ 

I was able to run this without any error and with "Verify SSL Certificate" set to "Yes".

HttpCaller_SSL 

The certificate is issued by "DigiCert High Assurance EV Root CA", Can you check if you have that vendor on your windows machined under Trusted Root Certification.


Hey guys!

 

Thanks for the quick response. Got a bit further but still an SSL error. @rahulsharma​  I've checken the trusted root and they are in there. I've also tried readding them in the proper places which I did but still not result.

trusted root 

The thing is when I post it to FME server it works. Seeing the responses here i'm getting the feeling that the issue is bounded to the specific server where i'm working on. Unfortunately the logging isn't pointing me in some direction to look. I can imagine its depends on Cipher suites oy maybe even TLS version. Its just that all browser work except the fme caller. How can I find the root cause to this issue?SSL conncet error 

I've also set up a proxy between it with self signed and even that works. It gets really weird. I'm out of option finding the problem. Anyone have some ideas?


Hey guys!

 

Thanks for the quick response. Got a bit further but still an SSL error. @rahulsharma​  I've checken the trusted root and they are in there. I've also tried readding them in the proper places which I did but still not result.

trusted root 

The thing is when I post it to FME server it works. Seeing the responses here i'm getting the feeling that the issue is bounded to the specific server where i'm working on. Unfortunately the logging isn't pointing me in some direction to look. I can imagine its depends on Cipher suites oy maybe even TLS version. Its just that all browser work except the fme caller. How can I find the root cause to this issue?SSL conncet error 

I've also set up a proxy between it with self signed and even that works. It gets really weird. I'm out of option finding the problem. Anyone have some ideas?

Hi @adriaan​ can you turn on Debug Logging to provide more info


Hi @adriaan​ ,

 

FME will give that error if that ciphers suite is not supported by the OS that you are using. Is your FME Server and Desktop hosted on different OS versions?

 

Richard had a good explanation on this question: https://community.safe.com/s/question/0D74Q0000082MikSAE/detail

 

"FME uses the ciphers installed on the operating system. We don't ship or support the ciphers. Most likely they will need to use a newer operating system to allow the connection. This link has details on what cyphers are included with various Windows operating systems."

 

In that question there is a workaround, however, it's only valid in newer versions of FME and isn't fully supported by us. Hopefully, this clears things up! Please let me know if you have any questions.

 

 


@adriaan Good morning. Did you ever find a solution to this issue you were having? I’m running into something similar. Thanks


@adriaan Good morning. Did you ever find a solution to this issue you were having? I’m running into something similar. Thanks

Found a solution today 

  1. Noticed that I couldn't get to the website from Internet Explorer from FME Flow Dev server.
    1. Opened website from FME flow Test server browser (Mozilla) and looked at page encryption details.
      1. Noted encryption cipher
    2. Opened IISCrypto.exe from FME flow Dev server and found that cipher wasn't checked in cipher suites list.
    3. Checked cipher checkbox and restarted FME flow Dev server.
    4. Was able to navigate to the site from the browser.
    5. Workspace navigating to site ran successfully.

Reply