SSL error with YouTube on n8n hosted on Docker for Mac

Describe the problem/error/question

Currently running an instance in Docker on Mac and I have this workflow to upload YouTube video using the Local File Trigger it triggers on file added previous nodes work fine but when its uploading to YouTube after X amount of seconds (testing with small file) it throws an SSL error the node fails and the corrupted file shows up on YouTube but of course it never renders.

Note: Tested same workflow but this time running on Docker using WSL and it works fine no SSL error at all as long as the folder is not on a mounted drive from Windows if its a mounted drive the Local File Trigger node will never trigger when a file is added.

What is the error message (if any)?

This is the error I’m getting:

Error: 58ABFC6ACC7F0000:error:0A0003FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 20

Edit: I Sometimes also get ERROR: read ECONNRESET

Error: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
    at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17)

Please share your workflow

Information on your n8n setup

The current setup I have is a Mac mini 2012 running Ventura with Cloudflare Tunnels + Nginx Proxy Manager to access with a domain and using latest n8n version (1.18.2)

  • n8n version: 1.18.2
  • Database (default: SQLite): postgres
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on Mac
  • Operating system: macOS Ventura

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hi @lonus, I am sorry for the trouble!

Seeing a combination of sslv3 alert bad record mac and ECONNRESET problems from time to time could suggest an unusual network connection.

I am not able to reproduce this myself on any of the machines I have access to unfortunately. Is there a chance your machine is running on a mobile network, behind any kind of captive portal (the latter is quite common in places like student accommodation or furnished business apartments for example) or using any kind of ad-supported broadband plan?

Are you also seeing this problem when enabling the retry option on your node? Like so:

Hi @MutedJam

No the machine is running directly through ethernet to the ISP router (home connection) no firewall or anything like that blocking the connection, I noticed that either restarting the machine or Docker entirely fixes this but its uncertain to when its gonna happened so far i notice it fails because I’m passing the error to error handler workflow that notifies me when a workflow fails.

And when retrying the execution either works fine or throws the ssl3 alert bad record or ECONNRESET error.

So far this does not happen on a Docker on Windows 11 with WSL (different machine), so it makes me thing that Mac os somehow messing up the connection while the workflow is still running, the only workaround I found for now is passing the data from the local file trigger to another instance on windows machine and do the heavy load there and see if this comes back.