API won't authenticate

  • 1
  • Problem
  • Updated 11 months ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: EOL CLEANUP

Getting this message when I try to authenticate or when someone tries to sign up: "Authorization failed: cURL error 35: error:14077410:SSL routines: SSL23_GET_SERVER_HELLO:s alert handshake failure
Photo of Justice & Mercy International

Justice & Mercy International

  • 6 Posts
  • 0 Reply Likes
  • confused

Posted 1 year ago

  • 1
Photo of Ben Harrington

Ben Harrington, Employee

  • 112 Posts
  • 12 Reply Likes
Hi There,
I just jumped into your account, and it looks like you do not currently have an API key generated in your account, so that would explain why the authentication is failing. If you go to your settings for the account and generate a new API key and input the new data into Bloom I think that should take care of it! 

If there are still issues authenticating once that has been done let me know! 

-Ben
Photo of Ben Harrington

Ben Harrington, Employee

  • 112 Posts
  • 12 Reply Likes
Hi There,
I just wanted to check in and see if my reply above allowed you to authenticate the connection with Bloom.

-Ben
Photo of Justice & Mercy International

Justice & Mercy International

  • 6 Posts
  • 0 Reply Likes
Hello! I've generated an api key, updated it on Bloom and still getting the same message. Thoughts?
Photo of Justice & Mercy International

Justice & Mercy International

  • 6 Posts
  • 0 Reply Likes
Photo of Ben Harrington

Ben Harrington, Employee

  • 112 Posts
  • 12 Reply Likes
Hi There,
My apologies for not responding sooner! Are you still having trouble with this? If you have entered in the correct API information I am unsure as to why there would be an authorization error, and this would be something that you would want to reach out to Bloom about, as we do not have any insight into what is happening with that error since they built that plugin. 

Let me know if you have any other questions! 

-Ben
Photo of TP

TP

  • 1 Post
  • 0 Reply Likes
Hello,

Im getting the similar error "Something misfired. Please check your API keys and try again, cURL error 35: SSL connect error"

see below of the screenshot. Im using the plugin: https://wordpress.org/plugins/emma-emarketing-plugin/




I believe something is up with the authenticaiton of the api. Wondering are you guys forcing SSL on website for auth?
Photo of Ben Harrington

Ben Harrington, Employee

  • 112 Posts
  • 12 Reply Likes
Hi There,
Sorry that I am just now responding to this, but we have seen this error pop up when a site is using a version of TLS that we do not support. In order to align with industry best practices for security and data integrity, we upgraded to using TLS 1.1 or higher as of August 16th, 2017. 

If you have not verified that your site is connecting using TLS 1.1+, your use of the API may be broken, thus causing the error. We recommend using TLS 1.2. 

I hope this helps! 

-Ben