FreshDesk SSL Handshake Error

[Pratik3311]

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

This is the error i am encoutering with.

Problem in node ‘Get Ticket Details‘

write EPROTO 40D22F379B7F0000:error:0A000410:SSL routines:ssl3_read_bytes:ssl/tls alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:916:SSL alert number 40

Information on your n8n setup

I am using n8n website not downloaded and executed from the local system , used the n8n cloud version

[hoiyothaheem]

This SSL/TLS handshake error (alert number 40) with FreshDesk typically indicates an API authentication or domain configuration issue rather than an actual SSL/TLS protocol problem.

Root Cause

The error “ssl3_read_bytes:ssl/tls alert handshake failure” with FreshDesk API usually means:

1. Incorrect API Key format - Most common
2. Wrong FreshDesk domain in credentials
3. API Key permissions issue

Solution Steps

1. Verify Your FreshDesk API Key

In FreshDesk:

1. Go to Profile Settings (top-right avatar)
2. Navigate to Profile Settings → Your API Key
3. Copy the full API key (should look like: xAbCdEfGh12345XyZ)

2. Check Your n8n FreshDesk Credentials

In n8n Cloud:

1. Go to Credentials → FreshDesk API
2. Domain: Should be ONLY your subdomain (e.g., yourcompany NOT yourcompany.freshdesk.com)
3. API Key: Paste the full API key from FreshDesk

Common Mistakes:
Domain: yourcompany.freshdesk.com (Wrong)
✓ Domain: yourcompany (Correct)

API Key: Partial key or with extra characters
✓ API Key: Full key exactly as shown in FreshDesk

3. Recreate FreshDesk Credentials

Sometimes credentials get corrupted:

1. Delete your existing FreshDesk credential in n8n
2. Generate a new API key in FreshDesk (if possible)
3. Create fresh credentials in n8n with correct format

4. Verify API Key Permissions

In FreshDesk, ensure your API key has:

• Ticket permissions (read/write)
• Contact permissions (read)
• Admin or Agent role (not Customer)

Quick Test

To verify your credentials work, test with a simple HTTP Request node:

GET https://yourcompany.freshdesk.com/api/v2/tickets
Authorization: Basic <base64 of apikey:X>

If this works but FreshDesk node fails, the issue is with credential configuration in n8n.

Why This Happens on n8n Cloud

n8n Cloud’s SSL/TLS implementation is stricter than self-hosted versions. When FreshDesk API rejects the authentication (wrong API key/domain), it closes the SSL connection immediately, triggering this confusing “SSL handshake” error instead of a clearer “401 Unauthorized” message.

Alternative: Use HTTP Request Node

If FreshDesk node keeps failing, use HTTP Request node with:

• URL: https://yourcompany.freshdesk.com/api/v2/tickets/{{ticket_id}}
• Authentication: Generic Credential Type
  • Header Auth
  • Name: Authorization
  • Value: Basic {{base64(apikey:X)}}

I’ve configured dozens of FreshDesk integrations for clients - 90% of SSL handshake errors are actually credential format issues, not real SSL problems.

Double-check your domain format (no .freshdesk.com) and API key, then try again. Let me know if you’re still stuck!

[Pratik3311]

thank you so much , the issue was with the company domain.

I was doing companyname.freshdesk.com
but need to use only company

[hoiyothaheem]

@Pratik3311 Perfect! Glad that fixed it!

Exactly as I suspected - the domain format was the culprit. The “SSL handshake error” was actually FreshDesk rejecting the connection due to the incorrect domain in the credentials.

For anyone else with this issue:

• Wrong: companyname.freshdesk.com
• Correct: companyname (subdomain only)

If you found this solution helpful, please mark it as the solution so others can find it easily!

Happy automating!