N8n node failed after update on Back Up Your n8n Workflows To Github

Questions
1

Problem :

I was running on n8n hosted instance version from June and I did update with latest version, and tried with 4 last versions, but it seems that my n8n node from getting all workflows do not work anymore on the proposed Back Up Your n8n Workflows To Github template.

What is the error message (if any)?

{
“errorMessage”: “The service refused the connection - perhaps it is offline”,
“errorDetails”: {
“rawErrorMessage”: [
“connect ECONNREFUSED ::1:5678”,
“connect ECONNREFUSED ::1:5678”
],
“httpCode”: “ECONNREFUSED”
},
“n8nDetails”: {
“nodeName”: “n8n”,
“nodeType”: “n8n-nodes-base.n8n”,
“nodeVersion”: 1,
“resource”: “workflow”,
“operation”: “getAll”,
“itemIndex”: 0,
“runIndex”: 0,
“time”: “06/09/2024 14:42:23”,
“n8nVersion”: “1.57.0 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: The service refused the connection - perhaps it is offline”,
" at Object.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1199:15)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at Object.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2084:20)“,
" at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:339:29)”,
" at Object.makeRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:354:24)“,
" at Object.cursorPagination (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/N8n/GenericFunctions.js:59:28)”,
" at RoutingNode.makeRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:359:32)“,
" at async Promise.allSettled (index 0)”,
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:158:35)“,
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:779:23)”
]
}
}

Please share your workflow

{
“meta”: {
“instanceId”: “b51c9ec4078452f48b19e47554279393964a09a93a7e66c968568d70b5cefc5a”
},
“nodes”: [
{
“parameters”: {
“filters”: {}
},
“id”: “926f0d45-31e5-4322-a9d8-36b8f8020076”,
“name”: “n8n”,
“type”: “n8n-nodes-base.n8n”,
“position”: [
1220,
460
],
“typeVersion”: 1,
“retryOnFail”: true,
“credentials”: {
“n8nApi”: {
“id”: “O1oXyU05gU2uW7B0”,
“name”: “n8n account”
}
}
}
],
“connections”: {},
“pinData”: {}
}

Share the output returned by the last node

{
“errorMessage”: “The service refused the connection - perhaps it is offline”,
“errorDetails”: {
“rawErrorMessage”: [
“connect ECONNREFUSED ::1:5678”,
“connect ECONNREFUSED ::1:5678”
],
“httpCode”: “ECONNREFUSED”
},
“n8nDetails”: {
“nodeName”: “n8n”,
“nodeType”: “n8n-nodes-base.n8n”,
“nodeVersion”: 1,
“resource”: “workflow”,
“operation”: “getAll”,
“itemIndex”: 0,
“runIndex”: 0,
“time”: “06/09/2024 14:42:23”,
“n8nVersion”: “1.57.0 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: The service refused the connection - perhaps it is offline”,
" at Object.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1199:15)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at Object.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2084:20)“,
" at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:339:29)”,
" at Object.makeRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:354:24)“,
" at Object.cursorPagination (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/N8n/GenericFunctions.js:59:28)”,
" at RoutingNode.makeRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:359:32)“,
" at async Promise.allSettled (index 0)”,
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:158:35)“,
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:779:23)”
]
}
}

Information on your n8n setup

  • n8n version: 1.57.0
  • Debug info

core

  • n8nVersion: 1.57.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.15.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

  • success: none
  • error: all
  • progress: false
  • manual: false
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 90 hours
  • maxCount: 10000 executions

Generated at: 2024-09-06T18:48:01.198Z

  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): via docker compose in a hosted vps
  • Operating system: ubuntu 22
2

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:
3

It’s already provided thanks

4

I got the idea to test with ss -tuln to see if the port is listen

It’s the case so I decided to switch the Base URL in n8n node connection
from http://localhost:5678/api/v1 to http://127.0.0.1:5678/api/v1

2 Likes
5

Thanks for sharing @Comps_Cedric !

I believe this is related to IPV6. Switich to 127.0.0.1 is indeed one way to skip the issue as your localhost is mapping to ::1 which is an abreviation for loopback in IPv6.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.