HTTP Request / OpenSSL Error

[jazarja]

Bug Description

When I sent a request to https://api.binance.com/api/v3/exchangeInfo using the HTTP request node, I received the following error:

write EPROTO 68ABEDB1527F0000:error:0A0003E8:SSL routines:ssl3_read_bytes:reason(1000):../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 0

Error Details

{
"errorMessage": "write EPROTO 68ABEDB1527F0000:error:0A0003E8:SSL routines:ssl3_read_bytes:reason(1000):../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 0\n",
"errorDetails": {
"httpCode": "rejected"
},
"n8nDetails": {
"nodeName": "HTTP Request",
"nodeType": "n8n-nodes-base.httpRequest",
"nodeVersion": 4.2,
"itemIndex": 0,
"time": "5/16/2024, 4:29:12 AM",
"n8nVersion": "1.39.1 (Self Hosted)",
"binaryDataMode": "default",
"stackTrace": [
"NodeApiError: write EPROTO 68ABEDB1527F0000:error:0A0003E8:SSL routines:ssl3_read_bytes:reason(1000):../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 0",
"",
" at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:1571:35)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:660:53",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1062:20"
]
}
}

To Reproduce

1. Add http request node
2. Set URL to https://api.binance.com/api/v3/exchangeInfo

Expected behavior

JSON file retrieved correctly.

Operating System

Not sure, Standard n8n Docker Image

n8n Version

1.39.1

Node.js Version

4.2

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @jazarja

What happens if you add the ignore ssl issues option?

Are you also using a vpn / proxy / running n8n on a company managed laptop?

[jazarja]

@Joffcom The same error persists even with the "ignore SSL issues" option activated.

I'm not using a VPN or proxy.

[Joffcom]

Hey @jazarja,

That is unusual, I am able ot access to it using from my n8n instance with no errors. Where are you running from as I can't see any reason for this to be an issue with n8n itself at the moment.

Have you checked your network configuration in Docker for anything odd and tried making the same request from CURL?