CURL SSL problem

I've got exception like that when I was trying to add leads via API:

"HTTP Error (60): SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed"

What could be cause that? Is it problem on my hosting side?

Thanks

0

Comments

13 comments
  • Official comment

    Thanks for reporting this issue. Our operations team is investigating this issue, so it should be resolved shortly. 

    Brian McConnell

    Insightly Engineering Team

    Comment actions Permalink
  • Any updates?

    0
    Comment actions Permalink
  • Hi, we looked into the issue but were not able to reproduce the problem. Is it possible you are using cached credentials? Can you make the request from a different machine? We have an automated test suite we run that does about 500 different test operations, and those all run fine. Thanks, Brian

    0
    Comment actions Permalink
  • What do you mean different machine? I'm using your API in my PHP script and getting that error exception...

    0
    Comment actions Permalink
  • Try running it on a different computer. As I mentioned, we can't reproduce the problem here, and aren't seeing anything weird in our test suites, so its helpful to rule out your local environment as a cause.

    You can also suppress this warning in cURL, it seems to be sensitive to issues like this where other HTTP/S utilities like Postman are not. 

    Thanks.

    Brian

    0
    Comment actions Permalink
  • there is nothing about computer...everybody gets this error. I use your API to create Leads from our website contact form, so it was like 30 unique customers get this error

    0
    Comment actions Permalink
  • As I said before, we ran our own test suite (500 automated tests) against the API (we do this every time we push an update to production). All of the tests pass. So we cannot reproduce this error here. 

    What I am suggesting you do is to run this script on a different computer and verify that you do not see a similar error (if your computer has an expired certificate cached locally, that would cause something like this). You can also disable SSL warnings in cURL, which, as I mentioned before, tends to generate warnings more than other tools like it. 

    Thanks,

    Brian

    0
    Comment actions Permalink
  • "if your computer has an expired certificate cached locally" - is this a joke?

    my computer doesn't have any certificates...and... is SSL certificate could be cached locally?:) I don't think so. I suspect there is a serious misleading

    0
    Comment actions Permalink
  • Like I said, we were not able to reproduce the problem locally, and we run several hundred tests against the API. I am just trying to help you rule out an issue with your local environment. And _once again_, I mentioned that you can disable this notification in cURL. Try Googling "ignore ssl warnings curl" for instructions on how to do this.

    0
    Comment actions Permalink
  • My hosting support team response: 

    "The error message that you were initially receiving, asking you to verify that the CA cert is OK, pointed us in the direction of insight.ly's SSL Certificate. As it turns out, several chains are broken in their SSL Certificate. See this screenshot:

    https://www.evernote.com/l/AcEGq54rkCRAzZ5iFCR8H8PbyYe1Xz-5Dao

    You can also search insight.ly's certificate on this site:

    https://www.digicert.com/help/

    Please reach out to them for assistance with this issue"

    So, it appears that the problem on your side... check your SSL chains...

    0
    Comment actions Permalink
  • Hi Vesalink!

    Thanks for keeping us updated. I'm going to create a support ticket for you so we can further assist. :)

    1
    Comment actions Permalink
  • Hi Nora,

    any updates? It's been almost a week since I create a post. WHY are you figuring out so slow? We are loosing the customers!

    0
    Comment actions Permalink
  • Hi Veralink,

    Our team was not able to reproduce this. A suggestion that was provided was to suppress the ssl warnings in curl. You can search "curl ignore ssl error" to learn how to do this. :)

    You can also eliminate dependencies on other software you may be using by making requests with the Postman extension for Chrome. 

    1
    Comment actions Permalink

Please sign in to leave a comment.