ElevenLabs API request fails with TLSSocket error on n8n server

Below are some troubleshooting steps you can follow:

1. Verify Network Connectivity

Ensure your n8n server can reach the ElevenLabs API endpoint. For example, from your server run a command like:

BASHCopied
curl -v https://api.elevenlabs.io/

This helps confirm there isn’t a network issue or a firewall/proxy blocking the connection.

2. Check TLS/SSL Settings

The error indicates the TLS connection was aborted. Make sure that:

• Your server’s certificate store is up to date.
• Any proxy or network device between your n8n server and the ElevenLabs API isn’t interfering with TLS handshakes.

3. Compare Server Configurations

Since the request works on one server but not on your n8n server (installed via EazyPanel in queue mode), verify if there are any differences:

• Environment Variables: Ensure that the ElevenLabs API key and any required configuration (such as AGENT_ID if applicable) are set correctly.
• Timeout Settings: Consider increasing the timeout or adding retry logic in your workflow in case network latency is an issue.

4. Examine n8n Logging and Queue Mode

Since n8n is running in queue mode:

• Check the logs (or EazyPanel logs) to see if the error occurs consistently or intermittently.
• Consider testing the ElevenLabs conversion outside of the queue mode to isolate if the environment is affecting the connection.

5. Firewall / Proxy Considerations

If your n8n server is behind a firewall or uses a proxy, ensure that outbound connections to ElevenLabs are permitted.

---

Following these steps should help you identify whether the issue is due to TLS/SSL configuration, network/firewall restrictions, or environmental differences between your servers. Adjust the configuration accordingly, and then test your text-to-audio conversion again.