[Bug]: Error while using Caption "Bad request - please check your parameters Cannot set attribute 'src' directly

[KhaledElzarw]

Describe the bug

I'm using n8n workflow trying to add captions to my videos. I have n8n, ncatoolkit, minio, ngrok and baserow hosted locally on docker on my pc. The setup used to be working perfectly fine until I decided to move minio, ngrok, and baserow to my raspberry pi to free up my RAM space and I upgraded the RAM later. My minio bucket is set to public

My_workflow.json

ever since I did that, other endpoints work fine but whenever I add captions I get
"Bad request - please check your parameters
Cannot set attribute 'src' directly. Use '_unsafe_update_src()' and manually clear .hash of all callersinstead.
{
"errorMessage": "Bad request - please check your parameters",
"errorDescription": "Cannot set attribute 'src' directly. Use '_unsafe_update_src()' and manually clear .hash of all callersinstead.",
"errorDetails": {
"rawErrorMessage": [
"400 - "{\"build_number\":184,\"code\":400,\"id\":null,\"job_id\":\"25428686-0a5e-41a6-bc74-2b962333ee45\",\"message\":{\"error\":\"Cannot set attribute 'src' directly. Use '_unsafe_update_src()' and manually clear .hash of all callersinstead.\"},\"pid\":9,\"queue_id\":129391764619952,\"queue_length\":0,\"queue_time\":0,\"response\":null,\"run_time\":6.056,\"total_time\":6.056}\n""
],
"httpCode": "400"
},
"n8nDetails": {
"nodeName": "Create Captions1",
"nodeType": "n8n-nodes-base.httpRequest",
"nodeVersion": 4.2,
"itemIndex": 0,
"time": "12/06/2025, 12:48:06 AM",
"n8nVersion": "1.93.0 (Self Hosted)",
"binaryDataMode": "default",
"stackTrace": [
"NodeApiError: Bad request - please check your parameters",
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:615:21)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:696:27)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:930:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1266:20"
]
}
}"

Reproduction Steps

Added a set node to stringify the variable before the caption node

I tried minimizing the payload to
{
"video_url": "http://host.docker.internal:9000/nca-toolkit/d222a852-dcdd-47a7-8b54-77a0a5647688_output_0.mp4"
}

Expected behavior

add captions to the video

Screenshots and relevant files

No response

Platform

Local

Would you like to work on this issue?

Yes

Checklist

• I have searched the open issues for duplicates.
• I have shown the entire traceback, if possible.

Additional Context

No response

[KhaledElzarw]

Hey @KhaledElzarw, just a heads-up — the Raspberry Pi uses an ARM architecture, not 64-bit x86, which is likely the cause of the issue you're seeing. @victorcatalin created a version that supports different architectures — you might want to check that out. Not sure if it fully resolves your issue, but it could help: #156

Thanks @HarrisonFisher . Just yo confirm, n8n, ncatoolkit are both hosted on my windows computer on docker not on the pi

I previously had n8n, nca toolkit, minio, baserow and ngrok hosted on my 10 yrs old 12 gb ram windows pc. It was working fine "rather barely working" but couldn't use the computer for anything else.

So I moved minio, baserow and ngrok to the pi as the data, database and network tunneling host while keeping tts kokoro, n8n and NCA toolkit on my pc for computing after upgrading the ram to 32 gb "ddr3 ehem..." and I'm using gtx 1070... rather very humble set up but it works fine... or at least it used to.

[HarrisonFisher]

sorry

[HarrisonFisher]

@KhaledElzarw did you use that video_url for other endpoints?

Maybe you need something like this?

{
  "video_url": "http://raspberrypi.local:9000/nca-toolkit/video.mp4"
}

[KhaledElzarw]

@HarrisonFisher

Man I tried everything... http://(pi ip address):not sure which port minio was on... and I switched back to minio hosted on docker on pc for testing and was calling docker.internal ip... same thing... last but not least I hardcoded a url that has public access from my google drive with a .mp4 extension ..... same exact thing

[balramjhapate]

I am experiencing the same issue. Please resolve it.

[KhaledElzarw]

I am experiencing the same issue. Please resolve it.

Out of curiosity.. what's your n8n version?

[KhaledElzarw]

@stephengpope a little help please?

[stephengpope]

@KhaledElzarw the issue thread here on github are for bugs with the toolkit itself, we don't provide support for issues with minio or on how to use the toolkit.

If you think there is a bug, we're happy to look at it. In that case we would need a very easy way to reproduce it and clear instruction on where the bug is.

If you need direct support please join the no-code architects community.

https://www.skool.com/no-code-architects

[KhaledElzarw]

hi @stephengpope, thanks for your response. I would love to provide a very easy way to produce it and clear insturctions .. can you please tell me which part needs clarification in my bug report and how can I give you an easy way to reproduce it

[stephengpope]

@KhaledElzarw unfortunately no, I wish we had unlimited time to do so but this is a free tool and our ability to provide those types of instructions is limited.