Décrire le problème/l’erreur/la question
Re-publication car l’original a été signalé pour avoir inclus l’URL interne du serveur Docling
![]()
J’essaie de connecter n8n à un serveur Dockling en utilisant un nœud « HTTP Request » configuré comme suit,
Method: POST
URL: {docling_url}/v1/convert/file
Authentication: None
Send Body: enabled
Body Content Type: Form-Data
Body Type: n8n Binary file
Body Name: files
Body Input Data Field Name: data
Le nœud d’entrée est « Read Files from Disk », qui transmet un fichier pdf en forme binaire.
Quel est le message d’erreur (le cas échéant) ?
Le nœud « HTTP Request » reste dans l’état « Executing » pendant exactement 5 min, puis affiche l’erreur,
« Problem in node ‘HTTP Request1’
The connection was aborted, perhaps the server is offline »
Voici les réponses du serveur Docling lors de l’exécution du workflow,
DEBUG:python_multipart.multipart:Calling on_part_begin with no data
DEBUG:python_multipart.multipart:Calling on_header_field with data[54:73]
DEBUG:python_multipart.multipart:Calling on_header_value with data[75:108]
DEBUG:python_multipart.multipart:Calling on_header_end with no data
DEBUG:python_multipart.multipart:Calling on_headers_finished with no data
DEBUG:python_multipart.multipart:Calling on_part_data with data[112:115]
DEBUG:python_multipart.multipart:Calling on_part_end with no data
DEBUG:python_multipart.multipart:Calling on_part_begin with no data
DEBUG:python_multipart.multipart:Calling on_header_field with data[171:190]
DEBUG:python_multipart.multipart:Calling on_header_value with data[192:222]
DEBUG:python_multipart.multipart:Calling on_header_end with no data
DEBUG:python_multipart.multipart:Calling on_headers_finished with no data
DEBUG:python_multipart.multipart:Calling on_part_data with data[226:227]
DEBUG:python_multipart.multipart:Calling on_part_end with no data
DEBUG:python_multipart.multipart:Calling on_part_begin with no data
DEBUG:python_multipart.multipart:Calling on_header_field with data[283:302]
DEBUG:python_multipart.multipart:Calling on_header_value with data[304:387]
DEBUG:python_multipart.multipart:Calling on_header_end with no data
DEBUG:python_multipart.multipart:Calling on_header_field with data[389:401]
DEBUG:python_multipart.multipart:Calling on_header_value with data[403:427]
DEBUG:python_multipart.multipart:Calling on_header_end with no data
DEBUG:python_multipart.multipart:Calling on_headers_finished with no data
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:98297]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:65536]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:95223]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:107502]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:235493]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:255964]
DEBUG:python_multipart.multipart:Calling on_part_data with data[0:24853]
Partager le résultat renvoyé par le dernier nœud
{
“errorMessage”: “The connection was aborted, perhaps the server is offline”,
“errorDetails”: {
“rawErrorMessage”: [
“timeout of 300000ms exceeded”,
“timeout of 300000ms exceeded”
],
“httpCode”: “ECONNABORTED”
},
“n8nDetails”: {
“nodeName”: “HTTP Request1”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.4,
“itemIndex”: 0,
“time”: “5/28/2026, 11:36:06 AM”,
“n8nVersion”: “2.14.2 (Self Hosted)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: The connection was aborted, perhaps the server is offline”,
" at ExecuteContext.execute (/usr/lib/node_modules/n8n/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:816:16)“,
" at processTicksAndRejections (node:internal/process/task_queues:104:5)”,
" at WorkflowExecute.executeNode (/usr/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)“,
" at WorkflowExecute.runNode (/usr/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:11)”,
" at /usr/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1670:27",
" at /usr/lib/node_modules/n8n/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2315:11"
]
}
}
Informations sur votre configuration n8n
- version n8n : 2.14.2
- Base de données (par défaut : SQLite) : N/A
- paramètre n8n EXECUTIONS_PROCESS (par défaut : own, main) : default
- Exécution de n8n via (Docker, npm, n8n cloud, application de bureau) : npm
- Système d’exploitation : Cachy OS