Visit the main Crossref website

Handshake_failure error in notifications

Hello and good day, I’m trying to activate notifications for newly created DOIs on our platform, I’m following this guide documentation/content-registration/verify-your-registration/notification-callback-service/ in the crossref page,
but I’m having an issue trying to test the endpoint, I’m following the steps until the “2. Test your endpoint” step.
I send the test request and it goes ok but the notification never arrives and when I query the notifications I get this this error
unable to complete notification: callback-notification
with this exception Received fatal alert: handshake_failure

If you want more information I’ll be happy to post what I have.

thanks for your time

Hello @gpinzon,

Could you let me know if you are still having this issue. I am not aware of any issues currently but I would be happy to investigate further for you if you have more information you can send me. What is your username you are using to create the endpoint against?


1 Like

Thank you for your help, I’m still having the issue, the username is morr, I created one endpoint in the test environment (this one test.crossref.o‎rg/notification-callback/exec/createNotificationCallback), and that went alright, but when I test that endpoint (using this test.crossref.o‎rg/notification-callback/exec/createNotificationCallback), it doesn’t work. When I query the notification callback attempts (using this test.crossref.o‎rg/notification-callback/exec/findNotificationCallbackAttempts) I see the error I described in the first post.

@pdavis can you help me?


So in the example you say you created an endpoint in the system using test.crossref.o‎rg/notification-callback/exec/createNotificationCallback. Is that one you used?

To create an endpoint point using cURL you would need to use "\

Then you test that using "https://test.crossref.o‎rg/notification-callback/exec/createNotificationCallback

1 Like

Hello Paul
Thanks you for your response, I posted the wrong link in my previous answer but I used the endpoint you mentioned and created the endpoint without issues, it’s when I test the endpoint using createNotificationCallback that doesn’t work, and after querying the notifications I see the error I mention in my first post Received fatal alert: handshake_failure

Also I wanna add that the endpoint was created successfully because when I query the notifications, the response mentions it, so it seems to be an issue sending the notification to our server

   "serviced":"2022-01-13 10:02:56.0",
   "notifyPayloadExpiration":"2022-01-20 10:02:56.0",
   "recordCreated":"2022-01-13 10:02:56.0",
   "recordUpdated":"2022-01-13 10:02:56.0"

@pdavis sorry to be so annoying but I’m stuck here, our endpoint works and the notification error doesn’t say much (and it doesn’t seem to be an error in our endpoint), just want to know what can I do to get the notification callback service working.

Hello @gpinzon,

Sorry for the delay I was checking in with a developer as I wasn’t sure on this one. He said that he thinks this is possibly something on your end as there are not any other similar problems being reported here.

He asked me to ask if you are using TLS 1.2? TLS versions 1.0 and 1.1 are no longer supported and as the issue is negotiating a secure connection this could be why.


Hi paul, thanks for your answer, our server is running in the latest TLS 1.3 version so I don’t think that could be the issue


So our developer is going to check that our library is updated to negotiate with 1.3, do you know if you are requiring a minimum of 1.3 which could cause the handshake error? If so could you try allowing 1.2 to see if that helps?

Thank you,

Hello Paul, thank you for your answer, our site works with TLS from 1.1 to 1.3, you can see out SSL results here
https:// www.ssllabs. com/ssltest/analyze.html?d=next.morressier. com&latest, also according to the site it seems to work with most java versions except with version 6, please let me know if you need more information.